Application layer safety message with geo-fence information

ABSTRACT

Disclosed are techniques for wireless communication. In an aspect, a user equipment (UE) can transmit a device-to-device (D2D) communication. The D2D communication can include an application layer message and the application layer message includes one or more data elements related to a geo-fence for the UE.

BACKGROUND

Various aspects described herein generally relate to wirelesscommunication systems, and more particularly, to determining a proximityto a geo-fence and optionally invoking actions based on the proximity.In some aspects the geo-fence can be determined based on receivedinformation in a device to device communication including an applicationlayer message.

Wireless communication systems have developed through variousgenerations, including a first-generation analog wireless phone service(1G), a second-generation (2G) digital wireless phone service (includinginterim 2.5G and 2.75G networks), a third-generation (3G) high speeddata, Internet-capable wireless service and a fourth-generation (4G)service (e.g., Long Term Evolution (LTE) or WiMax). There are presentlymany different types of wireless communication systems in use, includingCellular and Personal Communications Service (PCS) systems. Examples ofknown cellular systems include the cellular Analog Advanced Mobile PhoneSystem (AMPS), and digital cellular systems based on Code DivisionMultiple Access (CDMA), Frequency Division Multiple Access (FDMA), TimeDivision Multiple Access (TDMA), the Global System for Mobile access(GSM) variation of TDMA, etc.

A fifth generation (5G) mobile standard, also referred to as New Radio(NR), calls for higher data transfer speeds, greater numbers ofconnections, and better coverage, among other improvements. The 5Gstandard, according to the Next Generation Mobile Networks Alliance, isdesigned to provide data rates of several tens of megabits per second toeach of tens of thousands of users, with 1 gigabit per second to tens ofworkers on an office floor, for example. Several hundreds of thousandsof simultaneous connections should be supported in order to supportlarge sensor deployments. Consequently, the spectral efficiency of 5Gmobile communications should be significantly enhanced compared to thecurrent 4G standard. Furthermore, signaling efficiencies should beenhanced and latency should be substantially reduced compared to currentstandards.

Existing wireless hazard alert systems require always-on broadcast andapplication layer message processing resulting in increased powerconsumption and additional RF congestion. Hazard alerts may be relatedto vehicles and non-vehicle entities. For example, from June 2017 toJune 2018, 1.33 million collisions between vehicles and deer, elk, mooseor caribou occurred in the US. For example, deer-vehicle collisionsalone result in about 200 human deaths and $1.1 billion in propertydamage each year, with an additional $3 billion spent by state andfederal governments, insurance companies and drivers to reduce andmanage animal to vehicle collisions.

Leveraging 5G increased data rates, decreased latency, and speed plusdistance sensitive physical layer (PHY) and medium access control layer(MAC) (PHY-MAC), Vehicle-to-Everything (V2X) communication technologiesare being implemented to support various driving applications, such aswireless communications between vehicles, between vehicles and theroadside infrastructure, between vehicles and pedestrians, etc.Accordingly, it would be beneficial to leverage V2X communicationtechnologies to implement collision deterrence systems to reduce loss ofproperty and life.

SUMMARY

This summary identifies features of some example aspects, and is not anexclusive or exhaustive description of the disclosed subject matter.Whether features or aspects are included in, or omitted from thissummary is not intended as indicative of relative importance of suchfeatures. Additional features and aspects are described, and will becomeapparent to persons skilled in the art upon reading the followingdetailed description and viewing the drawings that form a part thereof.

In accordance with the various aspects disclosed herein, at least oneaspect includes, a method for wireless communication at a first userequipment (UE), including: receiving a device-to-device (D2D)communication from a second user equipment (UE) including an applicationlayer message, where the application layer message includes one or moredata elements related to a geo-fence for the second UE.

In accordance with the various aspects disclosed herein, at least oneaspect includes, a method for wireless communication at a user equipment(UE), including: transmitting a device-to-device (D2D) communication,where the D2D communication includes an application layer message, andwhere the application layer message includes one or more data elementsrelated to a geo-fence for the UE.

In accordance with the various aspects disclosed herein, at least oneaspect includes, a first user equipment (UE) including: a transceiver;at least one processor coupled to a memory and to the transceiver, theat least one processor in cooperation with the transceiver beingconfigured to: receive a device-to-device (D2D) communication from asecond user equipment (UE) including an application layer message, wherethe application layer message includes one or more data elements relatedto a geo-fence for the second UE.

In accordance with the various aspects disclosed herein, at least oneaspect includes, a user equipment (UE) including: a transceiver; atleast one processor coupled to a memory and to the transceiver, the atleast one processor in cooperation with the transceiver being configuredto: transmit a device-to-device (D2D) communication, where the D2Dcommunication includes an application layer message, and where theapplication layer message includes one or more data elements related toa geo-fence for the UE.

Other objects and advantages associated with the aspects disclosedherein will be apparent to those skilled in the art based on theaccompanying drawings and detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are presented to aid in the description ofexamples of one or more aspects of the disclosed subject matter and areprovided solely for illustration of the examples and not limitationthereof:

FIG. 1 illustrates an exemplary wireless communications system inaccordance with one or more aspects of the disclosure.

FIGS. 2A and 2B illustrate example wireless network structures,according to various aspects.

FIG. 3 illustrates an example of wireless communication devices in awireless communications system in accordance with aspects of thedisclosure.

FIG. 4 illustrates an example of communication between UEs in accordancewith aspects of the disclosure.

FIG. 5 illustrates an example communication flow between UEs inaccordance with aspects of the disclosure.

FIG. 6 illustrates an example interaction between different layers at atransmitting device and a receiving device in accordance with aspects ofthe disclosure.

FIG. 7 illustrates an example interaction between different layers at atransmitting device and a receiving device in accordance with aspects ofthe disclosure.

FIG. 8 is a block diagram illustrating various components of anexemplary UE according to at least one aspect of the disclosure.

FIG. 9 illustrates an exemplary proximity device, represented as aseries of interrelated functional modules in accordance with an aspectof the disclosure.

FIG. 10 illustrates data elements used in D2D messaging according toaspects of the disclosure.

FIG. 11 illustrates new messages used in D2D messaging according toaspects of the disclosure.

FIG. 12 illustrates example signaling between two UEs in accordance withaspects of the disclosure.

FIG. 13 illustrates example signaling between two UEs in accordance withaspects of the disclosure.

FIG. 14 illustrates example signaling between two UEs in accordance withaspects of the disclosure.

FIG. 15 illustrates an example flowchart of at least one method inaccordance with an aspect of the disclosure.

FIG. 16A illustrates an example flowchart of at least one method inaccordance with an aspect of the disclosure.

FIG. 16B illustrates an example flowchart of at least one method inaccordance with an aspect of the disclosure.

FIG. 17 illustrates an example device represented as a series ofinterrelated functional modules in accordance with an aspect of thedisclosure.

DETAILED DESCRIPTION

Disclosed are techniques for establishing a geofence that moves with theUE (e.g., vehicle-mounted UE, animal-mounted UE (e.g., tag), pedestrianUE, etc.) using 5G NR D2D communications. For example, C-V2Xcommunication enables one-to-one (device-to-device) and one-to-manyinfrastructure-less communication, as well as infrastructure-mediatedcommunication. The moving geofence by can be established by exposing 5GNR embedded controls from the physical layer (PHY) and/or media accesscontrol layer (MAC) also referred herein as PHY-MAC embedded controls tothe application layer. This allows for reduced device power consumptionby repurposing the 5G NR PHY-MAC control message mechanisms to enable ordisable application layer message processing. Specifically, when noviolation of the geo-fence is detected, messages may be blocked fromgoing to the application layer thereby preventing unnecessary messageprocessing at the application layer.

These and other aspects of the subject matter are provided in thefollowing description and related drawings directed to specific examplesof the disclosed subject matter. Alternates may be devised withoutdeparting from the scope of the disclosed subject matter. Additionally,well-known elements will not be described in detail or will be omittedso as not to obscure the relevant details.

The word “exemplary” is used herein to mean “serving as an example,instance, or illustration.” Any aspect described herein as “exemplary”is not necessarily to be construed as preferred or advantageous overother aspects. Likewise, the term “aspects” does not require that allaspects include the discussed feature, advantage, or mode of operation.

The terminology used herein describes particular aspects only and shouldnot be construed to limit any aspects disclosed herein. As used herein,the singular forms “a,” “an,” and “the” are intended to include theplural forms as well, unless the context clearly indicates otherwise.Those skilled in the art will further understand that the terms“comprises,” “comprising,” “includes,” and/or “including,” as usedherein, specify the presence of stated features, integers, steps,operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

Further, various aspects may be described in terms of sequences ofactions to be performed by, for example, elements of a computing device.Those skilled in the art will recognize that various actions describedherein can be performed by specific circuits (e.g., an applicationspecific integrated circuit (ASIC)), by program instructions beingexecuted by one or more processors, or by a combination of both.Additionally, these sequences of actions described herein can beconsidered to be embodied entirely within any form of non-transitorycomputer-readable medium having stored thereon a corresponding set ofcomputer instructions that upon execution would cause an associatedprocessor to perform the functionality described herein. Thus, thevarious aspects described herein may be embodied in a number ofdifferent forms, all of which have been contemplated to be within thescope of the claimed subject matter. In addition, for each of theaspects described herein, the corresponding form of any such aspects maybe described herein as, for example, “logic configured to” and/or otherstructural components configured to perform the described action.

As used herein, the terms “UE,” “vehicle UE” (V-UE), on-board unit (OBU)and “base station” are not intended to be specific or otherwise limitedto any particular radio access technology (RAT), unless otherwise noted.In general, the user devices will be referred herein as UEs and as suchUEs may be any wireless communication device (e.g., a vehicle onboardcomputer, a vehicle navigation device, a mobile phone, a router, atablet computer, a laptop computer, a tracking device, an Internet ofThings (IoT) device, etc.) used by a user to communicate over a wirelesscommunications network. A UE may be mobile or may (e.g., at certaintimes) be stationary, and may communicate with a radio access network(RAN). As used herein, the term “UE” may be referred to interchangeablyas an “access terminal” or “AT,” a “client device,” a “wireless device,”a “subscriber device,” a “subscriber terminal,” a “subscriber station,”a “user terminal” or UT, a “mobile terminal,” a “mobile station,” orvariations thereof. A V-UE or OBU may be any in-vehicle wirelesscommunication device, such as a navigation system, a warning system, aheads-up display (HUD), etc. Alternatively, a V-UE may be a portablewireless communication device (e.g., a cell phone, tablet computer,etc.) that belongs to the driver of the vehicle or a passenger in thevehicle. The term “V-UE” may refer to the in-vehicle wirelesscommunication device or the vehicle itself, depending on the context.Generally, UEs can communicate with a core network via a RAN, andthrough the core network the UEs can be connected with external networkssuch as the Internet and with other UEs. Of course, other mechanisms ofconnecting to the core network and/or the Internet are also possible forthe UEs, such as over wired access networks, WiFi networks (e.g., basedon IEEE 802.11, etc.) and so on.

A base station may operate according to one of several RATs incommunication with UEs depending on the network in which it is deployed,and may be alternatively referred to as an access point (AP), a networknode, a NodeB, an evolved NodeB (eNB), a general Node B (gNodeB, gNB),etc. In addition, in some systems a base station may provide purely edgenode signaling functions while in other systems it may provideadditional control and/or network management functions.

UEs can be embodied by any of a number of types of devices including butnot limited to printed circuit (PC) cards, compact flash devices,external or internal modems, wireless or wireline phones, smartphones,tablets, tracking devices, asset tags, and so on. A communication linkthrough which UEs can send signals to a RAN is called an uplink channel(e.g., a reverse traffic channel, a reverse control channel, an accesschannel, etc.). A communication link through which the RAN can sendsignals to UEs is called a downlink or forward link channel (e.g., apaging channel, a control channel, a broadcast channel, a forwardtraffic channel, etc.). As used herein the term traffic channel (TCH)can refer to either an uplink/reverse or downlink/forward trafficchannel.

FIG. 1 illustrates an exemplary wireless communications system 100according to one or more aspects. The wireless communications system100, which may also be referred to as a wireless wide area network(WWAN), may include various base stations 102 and various UEs 104. Thebase stations 102 may include macro cells (high power cellular basestations) and/or small cells (low power cellular base stations). Themacro cells may include Evolved NodeBs (eNBs) where the wirelesscommunications system 100 corresponds to an LTE network, gNodeBs (gNBs)where the wireless communications system 100 corresponds to a 5Gnetwork, and/or a combination thereof, and the small cells may includefemtocells, picocells, microcells, etc.

The base stations 102 may collectively form a RAN and interface with anevolved packet core (EPC) or next generation core (NGC) through backhaullinks. In addition to other functions, the base stations 102 may performfunctions that relate to one or more of transferring user data, radiochannel ciphering and deciphering, integrity protection, headercompression, mobility control functions (e.g., handover, dualconnectivity), inter-cell interference coordination, connection setupand release, load balancing, distribution for non-access stratum (NAS)messages, NAS node selection, synchronization, RAN sharing, multimediabroadcast multicast service (MBMS), subscriber and equipment trace, RANinformation management (RIM), paging, positioning, and delivery ofwarning messages. The base stations 102 may communicate with each otherdirectly or indirectly (e.g., through the EPC/NGC) over backhaul links134, which may be wired or wireless.

The base stations 102 may wirelessly communicate with the UEs 104. Eachof the base stations 102 may provide communication coverage for arespective geographic coverage area 110. In an aspect, although notshown in FIG. 1, coverage areas 110 may be subdivided into a pluralityof cells (e.g., three), or sectors, each cell corresponding to a singleantenna or array of antennas of a base station 102.

The term “cell” refers to a logical communication entity used forcommunication with a base station 102 (e.g., over a carrier frequency),and may be associated with an identifier for distinguishing neighboringcells (e.g., a physical cell identifier (PCID), an enhanced cellidentifier (E-CID), a virtual cell identifier (VCID), etc.) operatingvia the same or a different carrier frequency. In some examples, acarrier frequency may support multiple cells, and different cells may beconfigured according to different protocol types (e.g., machine-typecommunication (MTC), narrowband Internet-of-Things (NB-IoT), enhancedmobile broadband (eMBB), or others) that may provide access fordifferent types of devices. In some cases, the term “cell” may refer toa portion of a geographic coverage area 110 (e.g., a sector) over whichthe logical entity operates. As used herein, the term “cell” or “sector”may correspond to one of a plurality of cells of a base station 102, orto the base station 102 itself, depending on the context.

While neighboring macro cell geographic coverage areas 110 may partiallyoverlap (e.g., in a handover region), some of the geographic coverageareas 110 may be substantially overlapped by a larger geographiccoverage area 110. For example, a small cell base station 102′ may havea coverage area 110′ that substantially overlaps with the coverage area110 of one or more macro cell base stations 102. A network that includesboth small cell and macro cells may be known as a heterogeneous network.A heterogeneous network may also include Home eNBs (HeNBs) and/or HomegNodeBs, which may provide service to a restricted group known as aclosed subscriber group (CSG). The communication links 120 between thebase stations 102 and the UEs 104 may include uplink (UL) (also referredto as reverse link) transmissions from a UE 104 to a base station 102and/or downlink (DL) (also referred to as forward link) transmissionsfrom a base station 102 to a UE 104. The communication links 120 may useMIMO antenna technology, including spatial multiplexing, beamforming,and/or transmit diversity. The communication links may be through one ormore carriers. Allocation of carriers may be asymmetric with respect toDL and UL (e.g., more or less carriers may be allocated for DL than forUL).

The wireless communications system 100 may further include a wirelesslocal area network (WLAN) access point (AP) 150 in communication withWLAN stations (STAs) 152 via communication links 154 in an unlicensedfrequency spectrum (e.g., 5 gigahertz (GHz)). When communicating in anunlicensed frequency spectrum, the UEs 152 (WLAN STAs) and/or the WLANAP 150 may perform a clear channel assessment (CCA) prior tocommunicating in order to determine whether the channel is available.

The small cell base station 102′ may operate in a licensed and/or anunlicensed frequency spectrum. When operating in an unlicensed frequencyspectrum, the small cell base station 102′ may employ LTE or 5Gtechnology and use the same 5 GHz unlicensed frequency spectrum as usedby the WLAN AP 150. The small cell base station 102′, employing LTE/5Gin an unlicensed frequency spectrum, may boost coverage to and/orincrease capacity of the access network. LTE in an unlicensed spectrummay be referred to as LTE-unlicensed (LTE-U), licensed assisted access(LAA), or MulteFire.

The wireless communications system 100 may further include a mmW basestation 180 that may operate in mmW frequencies and/or near mmWfrequencies in communication with a UE 182. Extremely high frequency(EHF) is part of the RF in the electromagnetic spectrum. EHF has a rangeof 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10millimeters. Radio waves in this band may be referred to as a millimeterwave. Near mmW may extend down to a frequency of 3 GHz with a wavelengthof 100 millimeters. The super high frequency (SHF) band extends between3 GHz and 30 GHz, also referred to as centimeter wave. Communicationsusing the mmW/near mmW radio frequency band have high path loss and arelatively short range. The mmW base station 180 may utilize beamforming184 with the UE 182 to compensate for the extremely high path loss andshort range. Further, it will be appreciated that in alternativeconfigurations, one or more base stations 102 may also transmit usingmmW or near mmW and beamforming. Accordingly, it will be appreciatedthat the foregoing illustrations are merely examples and should not beconstrued to limit the various aspects disclosed herein.

The wireless communications system 100 may further include one or moreUEs, such as UE 190, that connects indirectly to one or morecommunication networks via one or more device-to-device (D2D)peer-to-peer (P2P) links. In the example of FIG. 1, UE 190 has a D2D P2Plink 192 with one of the UEs 104 connected to one of the base stations102 (e.g., through which UE 190 may indirectly obtain cellularconnectivity) and a D2D P2P link 194 with 'UE 152, a WLAN STA, connectedto the WLAN AP 150 (through which UE 190 may indirectly obtainWLAN-based Internet connectivity). In an example, the D2D P2P links192-194 may be supported with any well-known D2D RAT, such as LTE Direct(LTE-D), WiFi Direct (WiFi-D), Bluetooth, and so on.

Leveraging 5G increased data rates, decreased latency, and speed plusdistance sensitive physical layer (PHY) and medium access control layer(MAC) (PHY-MAC), Vehicle-to-Everything (V2X) communication technologiesare being implemented to support Intelligent Transportation Systems(ITS) applications, such as wireless communications between vehicles(Vehicle-to-Vehicle (V2V)), between vehicles and the roadsideinfrastructure (Vehicle-to-Infrastructure (V21)), and between vehiclesand pedestrians (Vehicle-to-Pedestrian (V2P)). The goal is for vehiclesto be able to sense the environment around them and communicate thatinformation to other vehicles, infrastructure, and personal mobiledevices. Such vehicle communication will enable safety, mobility, andenvironmental advancements that current technologies are unable toprovide. As discussed above, aspects disclosed herein may use geo-fencesto reduce collisions.

Still referring to FIG. 1, the wireless communications system 100 mayinclude multiple V-UEs 160 that may communicate with base stations 102over communication links 120 (e.g., using the Uu interface). V-UEs 160may also communicate directly with each other over a wireless sidelink162, with a roadside access point 164 over a sidelink 166, or with UEs104 over a sidelink 168 using P2P/D2D protocols (e.g., “PCS,” an LTE V2XD2D interface) or ProSe direct communications. Sidelink communicationmay be used for D2D media-sharing, V2V communication, V2X communication(e.g., cellular V2X (C-V2X) communication), emergency rescueapplications, etc. One or more of a group of V-UEs 160 utilizing D2Dcommunications may be within the geographic coverage area 110 of a basestation 102. Other V-UEs 160 in such a group may be outside thegeographic coverage area 110 of a base station 102 or be otherwiseunable to receive transmissions from a base station 102. In some cases,groups of V-UEs 160 communicating via D2D communications may utilize aone-to-many (1:M) system in which each V-UE 160 transmits to every otherV-UE 160 in the group. In some cases, a base station 102 facilitates thescheduling of resources for D2D communications. In other cases, D2Dcommunications are carried out between V-UEs 160 without the involvementof a base station 102.

In an aspect, the V-UEs 160, and any other UE illustrated in FIG. 1, mayhave a component 170 that determines proximity to a geo-fence alsoreferred to herein as geo- fence component 170. The geo-fence component170 may be a hardware, software, or firmware component that, whenexecuted, causes the V-UE 160 to perform the operations describedherein. For example, the geo-fence component 170 may be a softwaremodule stored in a memory of the V-UE 160 and executable by a processorof the V-UE 160. As another example, the geo-fence component 170 may bea hardware circuit (e.g., an ASIC, a field programmable gate array(FPGA), etc.) within the V-UE 160. Although discussed herein in thecontext of collision deterrence for explanation and illustrationpurposes, it will be appreciated that the geo-fence/proximity-basedfunctionality described herein may be used to perform otherfunctionalities.

In an aspect, the wireless sidelinks 162, 166, 168 may operate over acommunication medium of interest, which may be shared with othercommunications between other vehicles and/or infrastructure accesspoints, as well as other RATs. A “medium” may be composed of one or morefrequency, time, and/or space communication resources (e.g.,encompassing one or more channels across one or more carriers)associated with communication between one or more transmitter/receiverpairs.

In an aspect, the wireless sidelinks 162, 166, 168 may be C-V2X links. Afirst generation of C-V2X has been standardized in LTE, and the nextgeneration is expected to be defined in 5G (also referred to as “NewRadio” (NR) or “5G NR”). C-V2X is a cellular technology that alsoenables device-to-device communications. In the U.S. and Europe, C-V2Xis expected to operate in the licensed ITS band in sub-6GHz. Other bandsmay be allocated in other countries. Thus, as a particular example, themedium of interest utilized by sidelinks 162, 166, 168 may correspond toat least a portion of the licensed ITS frequency band of sub-6GHz.However, the present disclosure is not limited to this frequency band orcellular technology.

Other protocols for the wireless sidelinks 162, 166, 168 may includededicated short-range communications (DSRC) links. DSRC is a one-way ortwo-way short-range to medium-range wireless communication protocol thatuses the wireless access for vehicular environments (WAVE) protocol,also known as IEEE 802.11p, for V2V, V21, and V2P communications. IEEE802.11p is an approved amendment to the IEEE 802.11 standard andoperates in the licensed ITS band of 5.9 GHz (5.85-5.925 GHz) in theU.S. In Europe, IEEE 802.11p operates in the ITS G5A band (5.875-5.905MHz). Other bands may be allocated in other countries. The V2Vcommunications briefly described above occur on the Safety Channel,which in the U.S. is typically a 10 MHz channel that is dedicated to thepurpose of safety. The remainder of the DSRC band (the total bandwidthis 75 MHz) is intended for other services of interest to drivers, suchas road rules, tolling, parking automation, etc. Thus, as a particularexample, the mediums of interest utilized by sidelinks 162, 166, 168 maycorrespond to at least a portion of the unlicensed ITS frequency band of5.9 GHz.

Alternatively, the medium of interest may correspond to at least aportion of an unlicensed frequency band shared among various RATs.Although different licensed frequency bands have been reserved forcertain communication systems (e.g., by a government entity such as theFederal Communications Commission (FCC) in the United States), thesesystems, in particular those employing small cell access points, haverecently extended operation into unlicensed frequency bands such as theUnlicensed National Information Infrastructure (U-NII) band used bywireless local area network (WLAN) technologies, most notably IEEE802.11x WLAN technologies generally referred to as “Wi-Fi.” Examplesystems of this type include different variants of code divisionmultiple access (CDMA) systems, time division multiple access (TDMA)systems, frequency division multiple access (FDMA) systems, orthogonalFDMA (OFDMA) systems, single-carrier FDMA (SC-FDMA) systems, and so on.

Communications between the V-UEs 160 are referred to as V2Vcommunications, communications between the V-UEs 160 and the one or moreroadside access points 164 are referred to as V21 communications, andcommunications between the V-UEs 160 and one or more P-UEs 104 arereferred to as V2P communications. The V2V communications between V-UEs160 may include, for example, information about the position, speed,acceleration, heading, and other vehicle data of the V-UEs 160. The V21information received at a V-UE 160 from the one or more roadside accesspoints 164 may include, for example, road rules, parking automationinformation, etc. The V2P communications between a V-UE 160 and a P-UE104 may include information about, for example, the position, speed,acceleration, and heading of the V-UE 160 and the position, speed (e.g.,where the P-UE 104 is a bicycle), and heading of the P-UE 104. It willbe appreciated that terms, such as V-UE 160 and a P-UE 104 are usedherein for convenience of illustration and not limitation of specificapplications, device types, etc. It will be appreciated that thesedevices along with others referenced herein are also referred to usingthe general term UE, which applies to any of the user equipment devicesreferenced herein.

FIG. 2A illustrates an example wireless network structure 200 accordingto one or more aspects. For example, a Next Generation Core (NGC) 210can be viewed functionally as control plane functions 214 (e.g., UEregistration, authentication, network access, gateway selection, etc.)and user plane functions 212, (e.g., UE gateway function, access to datanetworks, IP routing, etc.) that operate cooperatively to form the corenetwork. User plane interface (NG-U) 213 and control plane interface(NG-C) 215 connect one or more gNBs 222 to the NGC 210 and specificallyto the control plane functions 214 and user plane functions 212. In anadditional configuration, one or more eNBs 224 may also be connected tothe NGC 210 via NG-C 215 to the control plane functions 214 and NG-U 213to user plane functions 212. Further, eNB(s) 224 may directlycommunicate with gNB(s) 222 via a backhaul connection 223. Accordingly,in some configurations, the New RAN 220 may only have one or more gNBs222, while other configurations include one or more of both eNBs 224 andgNBs 222. Either gNB(s) 222 or eNB(s) 224 may communicate with one ormore UEs 240 (e.g., any of the UEs depicted in FIG. 1, such as UEs 104,UE 152, UE 160, UE 182, UE 190, etc.). In an aspect, two UEs 240 maycommunicate with each other over a wireless unicast sidelink 242, whichmay correspond to wireless sidelink 162 in FIG. 1.

Another optional aspect may include a location management function (LMF)230 in communication with the NGC 210 to provide location assistance forUEs 240. The LMF 230 determines, using information from the UE 240and/or the New RAN 220, the current location of the UE 240 and providesit on request. The LMF 230 can be implemented as a plurality ofstructurally separate servers, or alternately may each correspond to asingle server. Although FIG. 2A illustrates the LMF 230 as separate fromthe NGC 210 and the New RAN 220, it may instead be integrated into oneor more components of the NGC 210 or the New RAN 220.

FIG. 2B illustrates an example wireless network structure 250 accordingto one or more aspects. For example, Evolved Packet Core (EPC) 260 canbe viewed functionally as control plane functions, i.e., MobilityManagement Entity (MME) 264, and user plane functions, i.e., Packet DataNetwork Gateway/Serving Gateway (P/SGW) 262, which operate cooperativelyto form the core network. S1 control plane interface (S1-MME) 265 and S1user plane interface (S1-U) 263 connect one or more eNBs 224 to the EPC260, and specifically to MME 264 and P/SGW 262, respectively.

In an additional configuration, one or more gNBs 222 may also beconnected to the EPC 260 via S1-MME 265 to MME 264 and S1-U 263 to P/SGW262. Further, eNB(s) 224 may directly communicate with one or more gNBs222 via the backhaul connection 223, with or without gNB directconnectivity to the EPC 260. Accordingly, in some configurations, theNew RAN 220 may only have gNB(s) 222, while other configurations includeboth eNB(s) 224 and gNB(s) 222. Either gNB(s) 222 or eNB(s) 224 maycommunicate with one or more UEs 240 (e.g., any of the UEs depicted inFIG. 1, such as UEs 104, UE 182, UE 190, etc.). In an aspect, two UEs240 may communicate with each other over a wireless sidelink 242, whichmay correspond to wireless unicast sidelink 162 in FIG. 1.

Another optional aspect may include a location server 270 that may be incommunication with the EPC 260 to provide location assistance for UE(s)240. In an aspect, the location server 270 may be an Evolved ServingMobile Location Center (E-SMLC), a Secure User Plane Location (SUPL)Location Platform (SLP), a Gateway Mobile Location Center (GMLC), or thelike. The location server 270 can be implemented as a plurality ofstructurally separate servers, or alternately may each correspond to asingle server. The location server 270 can be configured to support oneor more location services for UE(s) 240 that can connect to the locationserver 270 via the core network, EPC 260, and/or via the Internet (notillustrated).

FIG. 3 is a block diagram 300 of a first wireless communication device310 in communication with a second wireless communication device 350 viaV2V/C-V2X/V2X/D2D communication, e.g., via sidelink. The device 350 maycomprise a UE communicating with other another device 350 viaV2V/C-V2X/V2X/D2D communication, e.g., via sidelink. The first wirelesscommunication device 310 may comprise a UE communicating with anotherUE, e.g., device 350, via sidelink. In addition to the other componentsillustrated in FIG. 3, devices 310 and 350 may each comprise a messagecomponent 391, 393 and/or a determination component 392, 394 withingeo-fence component 170 or functionally cooperating with geo-fencecomponent 170. The message component 391, 393 may be configured togenerate a message having a first indication of a geographic areaassociated with the message, the geographic area based at least in parton the geographic location of the device 310, 350 that transmits themessage. The determination component 392, 394 may be configured todetermine whether the receiving device 310, 350 is within a thresholdrange of a transmitting device 310, 350 and/or to send a feedback forthe message based on the first indication of the geographic areaassociated with the message and the geographic location of the receivingdevice 310, 350. Packets may be provided to a controller/processor 375that implements layer 3 and layer 2 functionality. Layer 3 includes aradio resource control (RRC) layer, and layer 2 includes a packet dataconvergence protocol (PDCP) layer, a radio link control (RLC) layer, anda medium access control (MAC) layer.

The transmit (TX) processor 316 and the receive (RX) processor 370implement layer 1 functionality associated with various signalprocessing functions. Layer 1, which includes a physical (PHY) layer,may include error detection on the transport channels, forward errorcorrection (FEC) coding/decoding of the transport channels,interleaving, rate matching, mapping onto physical channels,modulation/demodulation of physical channels, and MIMO antennaprocessing. The TX processor 316 handles mapping to signalconstellations based on various modulation schemes (e.g., binaryphase-shift keying (BPSK), quadrature phase-shift keying (QPSK),M-phase-shift keying (M-PSK), M-quadrature amplitude modulation(M-QAM)). The coded and modulated symbols may then be split intoparallel streams. Each stream may then be mapped to an OFDM subcarrier,multiplexed with a reference signal (e.g., pilot) in the time and/orfrequency domain, and then combined together using an Inverse FastFourier Transform (IFFT) to produce a physical channel carrying a timedomain OFDM symbol stream. The OFDM stream is spatially precoded toproduce multiple spatial streams. Channel estimates from a channelestimator 374 may be used to determine the coding and modulation scheme,as well as for spatial processing. The channel estimate may be derivedfrom a reference signal and/or channel condition feedback transmitted bythe device 350. Each spatial stream may then be provided to a differentantenna 320 via a separate transmitter 318TX. Each transmitter 318TX maymodulate an RF carrier with a respective spatial stream fortransmission.

At the device 350, each receiver 354RX receives a signal through itsrespective antenna 352. Each receiver 354RX recovers informationmodulated onto an RF carrier and provides the information to the receive(RX) processor 356. The TX processor 368 and the RX processor 356implement layer 1 functionality associated with various signalprocessing functions. The RX processor 356 may perform spatialprocessing on the information to recover any spatial streams destinedfor the device 350. If multiple spatial streams are destined for thedevice 350, they may be combined by the RX processor 356 into a singleOFDM symbol stream. The RX processor 356 then converts the OFDM symbolstream from the time-domain to the frequency domain using a Fast FourierTransform (FFT). The frequency domain signal comprises a separate OFDMsymbol stream for each subcarrier of the OFDM signal. The symbols oneach subcarrier, and the reference signal, are recovered and demodulatedby determining the most likely signal constellation points transmittedby device 310. These soft decisions may be based on channel estimatescomputed by the channel estimator 358. The soft decisions are thendecoded and deinterleaved to recover the data and control signals thatwere originally transmitted by device 310 on the physical channel. Thedata and control signals are then provided to the controller/processor359, which implements layer 3 and layer 2 functionality.

The controller/processor 359 can be associated with a memory 360 thatstores program codes and data. The memory 360 may be referred to as acomputer-readable medium. The controller/processor 359 may providedemultiplexing between transport and logical channels, packetreassembly, deciphering, header decompression, and control signalprocessing. The controller/processor 359 is also responsible for errordetection using an ACK and/or NACK protocol to support HARQ operations.

Similar to the functionality described in connection with thetransmission by device 310, the controller/processor 359 may provide RRClayer functionality associated with system information (e.g., MIB, SIBs)acquisition, RRC connections, and measurement reporting; PDCP layerfunctionality associated with header compression/decompression, andsecurity (ciphering, deciphering, integrity protection, integrityverification); RLC layer functionality associated with the transfer ofupper layer PDUs, error correction through ARQ, concatenation,segmentation, and reassembly of RLC SDUs, re-segmentation of RLC dataPDUs, and reordering of RLC data PDUs; and MAC layer functionalityassociated with mapping between logical channels and transport channels,multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs,scheduling information reporting, error correction through HARQ,priority handling, and logical channel prioritization.

Channel estimates derived by a channel estimator 358 from a referencesignal or feedback transmitted by device 310 may be used by the TXprocessor 368 to select the appropriate coding and modulation schemes,and to facilitate spatial processing. The spatial streams generated bythe TX processor 368 may be provided to different antenna 352 viaseparate transmitters 354TX. Each transmitter 354TX may modulate an RFcarrier with a respective spatial stream for transmission.

The transmission is processed at the device 310 in a manner similar tothat described in connection with the receiver function at the device350. Each receiver 318RX receives a signal through its respectiveantenna 320. Each receiver 318RX recovers information modulated onto anRF carrier and provides the information to a RX processor 370.

The controller/processor 375 can be associated with a memory 376 thatstores program codes and data. The memory 376 may be referred to as acomputer-readable medium. The controller/processor 375 providesdemultiplexing between transport and logical channels, packetreassembly, deciphering, header decompression, control signalprocessing. The controller/processor 375 is also responsible for errordetection using an ACK and/or NACK protocol to support HARQ operations.

Wireless communication may include multicast communication directlybetween UEs. As an example, multicast sidelink communication may beperformed via a PC5 interface. UEs may communicate using sidelinkmulticast based on V2X communication, V2V communication, or D2Dcommunication, for example. A multicast may involve a transmission fromone UE that is intended to be decoded by UEs that are part of a servicegroup. A service group may comprise one or more UEs. A group IDidentifying the service group may be comprised in the message, e.g., inSidelink Control Information (SCI) of the multicast message, and/or aspart of the MAC layer destination address.

In a PC5 multicast, a transmitting UE may ensure that all intendedreceivers in the service group and in proximity of the transmitting UEaccurately receive the message. If the intended receivers in the servicegroup that are in the proximity of the transmitting UE do not receivethe message accurately, the transmitting UE may retransmit the messagein order to ensure accurate receipt of the message.

In order to improve reliability, feedback may be sent back from thereceiving UEs in the service group. For example, if a particular UE inthe service group does not correctly receive the message, the UE maytransmit a NACK, e.g., via sidelink, indicating to the transmitting UEthat there was an error in receiving the message. In response to theNACK, the transmitting UE may retransmit the message.

FIG. 4 illustrates an example of communication 400 between multiple UEs,e.g., based on C-V2X/V2X/V2V/D2D communication. UE 402 may be atransmitting UE that multicasts message 414 for a service group. UEs404, 406, and 408 may be associated with the service group. UE 404 mayhave correctly received the message 414 and does not transmit a NACK. UE406 may have experienced an error in receiving the message. Thus, UE 406may transmit a NACK 416 indicating to UE 402 that the message was notaccurately received. In response to the NACK 416, the transmitting UE402 may determine, e.g., at 424, to retransmit the message 414. However,negative feedback, e.g., NACK(s), may be received from far awayreceivers that are outside the desired proximity of the transmitting UE402. As illustrated in FIG. 4, the UE may intend for UEs withinrange/area 401 to receive the message reliably. UE 408 that is outsidethe intended area 401 and that is not proximate to UE 402 may receive atleast a part of the message and send a NACK 420 to UE 402. However, UE408 may be at such a distance that UE 408 will likely never receive themessage 414 correctly even with a retransmission from UE 402.Additionally, based on the service requirement, there may be no need forthe UE at that distance, e.g. UE 408, to receive the message, becausethe message becomes irrelevant.

Thus, NACK(s) may be received from receiving UEs associated with theservice group yet that are at such a distance that it would be futilefor the transmitter to retransmit the message. Such futileretransmissions would degrade overall system performance through aninefficient use of wireless resources and through unnecessary potentialinterference to other wireless communication. While a group ID, e.g., acommon destination ID, may be used to identify a multicast servicegroup, in an ad hoc C-V2X/V2X/V2V/D2D environment, it may be difficultto manage or establish a common group identifier that is known only tovehicles in the service group that are also in the proximity of thetransmitting UE because of the highly mobile nature of the transmittersand/or receivers.

Aspects are presented that limit feedback from receivers, e.g.,receiving UEs, outside of an intended geographical area by providinginformation that enables a receiver to determine whether it is anintended receiver of the message. The receiver can then determinewhether to send feedback based on whether or not the receiver is anintended receiver of the message. A transmitting device, e.g., 402, mayindicate geographic area information in each multicast messageindicating that receivers, e.g., 404, 406 that are within the indicatedgeographic area, e.g., 401, are intended to receive the message reliablyand should send feedback to help improve the multicast. This may help areceiver outside of the intended area, e.g., UE 408, to determine thatit does not need to send feedback. Thus, the geographic area informationhelps to limit feedback from receivers in the service group that are notin proximity to the transmitter. While the problems have been describedusing an illustration of C-V2X/V2X/V2V/D2D communication between UEs402, 404, 406, 408, the concepts are equally applicable to a basestation, RSU, mobile UE, vehicle UE etc. that are engaged in PC5 basedcommunication.

In order to reduce the amount of overhead to encode the geographic areainformation in the message, the geographic area may be indicated usingpredefined zones or areas. For example, a geographic area may be dividedinto a series of rectangular zones of uniform size. The geographic areamay be limited or could extend to encompass the entire earth surface.However, the various aspects disclosed herein are not limited theseexamples. The predefined zones or areas, for example, a zone ID or anarea ID may be encoded in the message. In one example, the zone/areaintended to reliably receive the message may comprise a circular areacentered on the location of the transmitting device, e.g., UE 402 orother transmitter engaged in PC5 communication, and extending to aradius indicated to the receiving devices. In another example,predefined zones may have a non-circular shape, e.g., with a regiondivided into a set of rectangular, hexagon, or other shaped zones, eachhaving a corresponding zone ID. In yet another example, the predefinedzones may have a customized shape. For example, the predefined zones mayfollow a contour of a road, a driving direction, a shape of a geographicfeature, etc. In another example, hierarchical zones may be organized indifferent layers. Each layer may correspond to zones of a differentsize. For example, first layer may correspond to zones having a radiusof 50 m, a width of 50 m, etc. A second layer may correspond to zoneshaving a radius of 100 m, a width of 100 m, etc. A third layer maycorrespond to zones having a radius of 500 m, a width of 500 m, etc.Thus, the transmitting device and receiving device may identify thezone/area that is intended for reliable reception of the message basedon a combination of a layer ID and a zone ID corresponding to the layerID. In another example, zone divisions may be pre-configured to thereceiving devices. For example, the zone divisions may be based onglobal coordinates of the geographic location. Then, the transmittingdevice may select a corresponding zone from among the pre-configuredzone divisions. Receiving and transmitting devices may receiveoccasional updates for the pre-configured zone divisions.

FIG. 5 illustrates an example communication flow 500 between atransmitting device 502 and a receiving device 504. The communicationmay be based on C-V2X/V2X/V2V/D2D communication, e.g., PC5 multicast,unicast and/or broadcast communication. In some aspects, thecommunication may be based on other D2D direct communication, such asProSe. Although FIG. 5 illustrates an example of communication between atransmitting device 502 and a receiving device 504 that are illustratedas UEs, the concepts are equally applicable to a base station, an RSU, amobile UE, a vehicle UE, etc. that are engaged in PC5 basedcommunication, C-V2X/V2X/V2V communication or other direct D2Dcommunication. As part of generating a service group message fortransmission, e.g., via C-V2X/V2X/V2V/D2D, the transmitting device 502may determine a zone/area/range for which the message is intended to bereliably received by a receiver in the service group. This may provide away for the transmitting device 502 to limit feedback to only areceiver(s) within the intended zone/area/range. The transmitting devicemay determine its current geographic location, at 503, and may use thecurrent location to determine an area/zone/range that is intended toreceive the message and for which the transmitting device should receiveHARQ feedback. For example, the transmitting device may identify apreconfigured zone in which the transmitting device is currentlylocated. In another example, the zone may be centered on thetransmitting device with a selected radius. In another example, thetransmitting device may define the zone in another manner or otherwiseselect the area/range/zone.

As one example, a range may be selected, e.g., based on a Quality ofService (QoS) parameter associated with the multicast. For example, the5QI for different services may indicate QoS information such as any of aresource type, a priority level for communication, a packet delay budget(PDB) indicating an amount of time that a packet can be delayed, aPacket Error Rate (PER) that indicates a limit on a rate of packetlosses, an averaging window, a data burst volume parameter thatindicates a limit on the amount of data to be served within a period oftime. In addition, the application may indicate a range requirement forthe traffic. For example, the range could be in the form of absolutedistance, e.g. 500 meters, or in relative levels, e.g. long, medium, orshort.

The transmitting device may indicate its current location and asurrounding range in the message. These may be indicated as a zone IDbased on the transmitting device's geographical location and a range ofthe surrounding zones. For example, the transmitting device may indicatean amount or a number, N, of adjacent surrounding zones that areintended to receive the message reliably. If N=1, then the receivingdevice would need to be within the same zone as the transmitting devicein order to be expected to reliably receive the message. If N=2, then areceiving device within the same zone as the transmitting device andwithin a zone directly adjacent to the zone of the transmitting devicewould be expected to reliably receive the message. For example, if thezones are of a rectangular shape, the devices expected to reliablyreceive the message should be in the same zone of the transmittingdevice and the 8 adjacent zones. If the zones are of a hexagon shape,the devices expected to reliably receive the message should be in thesame zone of the transmitting device and the 6 adjacent zone. N may beselected to be any number and is not limited to the examples providedherein.

Once the transmitting device has determined the zone/area/range intendedto reliably deliver the message and within which a receiver should sendfeedback, the transmitting device may generate the message. The messagemay comprise a control portion and a data portion. The control portionmay comprise in the Sidelink Control Information (SCI) an indication ofthe area/zone/range intended to reliably receive the message. The SCImay also include group ID information corresponding to the service groupfor the multicast. The group ID information may enable the message to bedecoded by receivers that are associated with the service group and thatknow the group ID. The group ID may be the same as a destination ID ormay be different than a destination ID. The group ID may be provided byan application layer, or a mid-ware layer of the UE, or mapped by theV2X layer from the ID provided by the application layer. The group IDmay correspond to a higher layer ID or an ID mapped from the higherlayer ID, whereas the destination ID corresponds to a lower layer ID.The group ID may be mapped to a destination ID.

In order to further reduce the overhead of transmitting thezone/area/range information in the message, the transmitting device mayhash the group ID and the zone ID, at 507, to generate a shortened ID,e.g., an Information Element (IE). The IE may then be embedded in theSCI of the message as part of the generation of the message at 509.After generation at 509, the transmitting device 502 may transmit themessage 511, along with the IE.

Receiving device 504 decodes at least a portion of the message, at 519,in order to determine the indication of the range/area/zone intended toreceive the message reliably, e.g., zone ID information. The receivingdevice might receive the control portion of the message, but might notcorrectly receive the data portion of the message. As the message is notreceived correctly, the receiving device 504 may need to determinewhether to send HARQ feedback, e.g., a NACK, to the transmitting device502. The receiving device may determine, at 521, whether to send a NACKbased on a current location of the receiving device and based on theindication, included in the message, of the range/area/zone intended toreceive the message reliably. Thus, the receiving device may determineits current location, at 517 and may determine to send a NACK when thereceiving device 504 is within the indicated range/area/zone. Forexample, the receiving device may send a NACK if the receiving device isin the same zone as the transmitting device, e.g., when N=1, or within alist of surrounding zones, when N>1. The surrounding zones may be basedon a range/number/amount indicated to the receiving device 504. Inanother example, the range/number/amount of surrounding zones may be afunction of a QoS for the multicast service. The QoS may be configuredvia RRC or via an upper layer.

The area/zone/range indicated in the message 511 may reference at leastone preconfigured zone, the preconfigured zones being preconfigured andstored at the receiving device. As illustrated at 513, the receivingdevice may receive an update of the preconfiguredzone(s)/area(s)/range(s). Although not illustrated, the transmittingdevice 502 may receive similar updates of the preconfiguredzone(s)/area(s)/range(s). At times a device may operate as atransmitting device, and at other times, the same device may operate asa receiving device.

When the indication of the area and/or group ID is comprised in an IE,the receiving device 504 may monitor for at least one IE in SCI of anyreceived messages, at 515. The IE(s) for which the receiving devicemonitors, at 515, may be based on a predetermined hash of any group IDfor multicast services with which the receiving UE is associated hashedwith surrounding zone IDs. As the receiving device may be mobile, thesurrounding zone IDs may be updated based on the receiving device'scurrent location.

If the UE determines, at 521, that the UE is within the area/zone/rangeof intended reliable receipt of the message, and the UE has notcorrectly received the message 511, the UE may respond with a NACK 523to the transmitting device 502. The UE may determine whether to send theNACK based on additional aspects, e.g., whether the receiver isassociated with the service group corresponding to a group ID comprisedin the message, etc. In response to the NACK 523, the transmittingdevice 502 may retransmit the message 525 in order to ensure reliablereceipt of the message by the receiving device 504.

FIGS. 6 and 7 illustrate examples of interaction between differentlayers at a transmitting device and a receiving device for the use of azone ID for C-V2X/V2X/V2V communication. Although the aspects arepresented for a V2X example, the aspects may be applied to other directD2D communication. In the example 600 in FIG. 6, application layer 602,Layer 3 for D2D communication, e.g., a V2X layer, 604, and AccessStratum (AS) layer 606 are for the transmitting device, e.g., 502. Inone example Layer 3 may comprise a V2X layer. In other examples, aspectsmay be applied to other D2D direct communication, such as ProSe.Application layer 608, Layer 3 for D2D communication, e.g., a V2X layer,610, and AS layer 612 are for the receiving device, e.g., 504. At thetransmitting device, the application layer may provide a group ID and aQoS profile for a particular service group to the Layer 3. The QoSprofile may include any of an indication of 5QI for the service group, arate for the service group, and/or a range for the service group. Theapplication layer 602 may also provide data to the Layer 3 to betransmitted in a message, e.g., a multicast message, to the servicegroup. The data may be provided with a corresponding group ID. Theapplication layer may provide a Provider Service Identifier (PSID) withthe data. The Layer 3 may map the group ID received from the applicationlayer to a Destination L2 ID (Dst. L2 ID) for the service group. TheLayer 3 may also store the QoS profile for the service group. If theLayer 3 does not provide a QoS Profile to the Layer 3, the Layer 3 mayuse the PSID to determine a corresponding QoS Profile, e.g., mapping thePSID to a QoS profile. As well, if the application layer does notprovide a Group ID to the Layer 3, the Dst. L2 ID determined by theLayer 3 may be based on a mapping of the PSID to the Dst. L2 ID. Suchmapping information can be pre-configured on the UE, stored in the(U)SIM card, or provisioned from the network via a dynamic provisioningmechanism, e.g. Open Mobile Alliance (OMA) Device Management (DM) OMA-DMor UE Policy delivery mechanism. The AS layer may receive the Dst. L2ID, a Source L2 ID, the QoS profile (e.g., including the 5QI and/orrange), and data for the service group from the Layer 3. The AS layermay determine whether to use an acknowledgement mode for the multicast,e.g., a NACK mode, based on the 5QI from the QoS profile or localpolicy. For example, if the 5QI indicates a requirement for highreliability, e.g., very low PER value, the transmitting UE may choose touse the acknowledgement to achieve such high reliability. In the NACKmode, the transmitting device may monitor for feedback, e.g. NACK(s), inorder to determine whether to retransmit the message. The AS layer 606may also determine a zone ID to use in the message. The zone ID maycorrespond to a zone in which the transmitting device is currentlylocated. The AS layer 606 may also determine a range to use in themessage. The range may indicate an additional range either surroundingthe transmitting device, or the zone or list of zones in which thereceiving device is located, for which the transmitting device intendsthe message to be reliably received. The range may inform a receiverwhether or not it should provide feedback. The transmitting device maythen transmit the message, comprising SCI 614 and data 616. The SCI mayinclude information indicating group ID or Dst. L2 ID, the zone IDdetermined by the AS, and/or the range determined by the AS.

At the receiving device, the application layer 608 provides a group ID,for a service group of which the receiving device is associated, to theLayer 610. The Layer 610 determines a Dst. L2 ID based on the group ID,similar to the mapping performed by the transmitting device's Layer 604.The AS layer 612 at the receiving device determines its own zone ID,e.g. for the zone in which the receiving device is currently located.When the receiving device receives the message, including the SCI 614and the data 616, the receiving device determines whether to sendfeedback, e.g., a NACK, if the data part of the message is not receivedcorrectly. The receiving device may determine whether to send the NACKbased on whether the Dst. L2 ID determines by Layer 610 matches the Dst.L2 ID indicated in the SCI 614 of the message and/or based on whetherthe zone ID for the receiving device that was determined by the AS 612matches the zone ID indicated in the SCI 614 or falls within the rangeof the zone ID indicated in the SCI 614. If the Dst. L2 IDs match andthe zone ID of the receiving device falls within the indicated range ofthe zone ID of the transmitting device, the receiving device may providea NACK if the data portion of the message is not received, for example.If no Dst. L2 ID is not provided from the Layer 610 to the AS layer 612at the receiving device, the receiving device may determine not to senda NACK. The SCI may carry the information regarding the Zone ID, Dst. L2ID, and range in different forms. For example, the zone ID and Dst. L2ID of the SCI may be hashed to reduce the overhead required to send themessage. In that case, the SCI may be of a different format than thatused for other V2X message transmission, e.g. broadcast messages.Therefore, an additional bit in SCI may be included in order todifferentiate the format of the message, e.g., whether the message isbroadcast, multicast, or unicast.

The example 700 in FIG. 7 is similar to the example in FIG. 6. Theapplication layer 702 and the Layer 3 for D2D communication, e.g., a V2Xlayer, 704 at the transmitting device may function similarly to theexample in FIG. 6. In one example Layer 3 may comprise a V2X layer. Inother examples, aspects may be applied to other D2D multicastcommunication., such as ProSe. However, in FIG. 7, the range might notbe determined or indicated by the AS layer 706 at the transmittingdevice. Instead, application layer 708 at the receiving device mayprovide a QoS profile for the service group to layer 710 at thereceiving device. The 5QI and range information may be provided from thelayer 710 to the AS layer 712 of the receiving device. The AS layer atthe receiving device may then determine not only its own zone ID basedon the receiving device's current location, but also the range to beused in determining whether to send feedback. Thus, the SCI 714 sentalong with the data 716 from the transmitting device might not includeinformation indicating the range. The receiving device may determinewhether to send feedback based on any combination of whether the Dst. L2ID of the SCI matches that determined by the layer 710, whether the zoneID determined by the AS 712 is within either the zone ID indicated inthe SCI 714 plus the range determined by the AS layer 712.Alternatively, the receiving device may determine a range based on itsown zone ID, and verify if the zone ID indicated in SCI 714 is withinthe range. For example, the receiving device might determine not to senda NACK if the Zone ID in the SCI 714 is not in the range of its own zoneID. As explained above, the SCI may include other information to supportthe operation. For example, it may include an indication of whether themessage is a retransmitted message, and a sequence number for themessage. In this case, the receiving device may determine whether tosend a NACK based on whether it has already received the originaltransmission of the same message.

FIG. 8 is a block diagram illustrating various components of anexemplary UE 800, according to aspects of the disclosure. In an aspect,the UE 800 may correspond to any of UEs described herein, for example,104, 152, 160, 182, 190 in FIG. 1, UEs 240 in FIGS. 2A and 2B, or UEs310, 350 in FIG. 3, etc. For the sake of simplicity, the variousfeatures and functions illustrated in the block diagram of FIG. 8 areconnected together using a common bus that is meant to represent thatthese various features and functions are operatively coupled together.Those skilled in the art will recognize that other connections,mechanisms, features, functions, or the like, may be provided andadapted as necessary to operatively couple and configure an actual UE.Further, it is also recognized that one or more of the features orfunctions illustrated in the example of FIG. 8 may be furthersubdivided, or two or more of the features or functions illustrated inFIG. 8 may be combined.

The UE 800 may include at least one transceiver 804 connected to one ormore antennas 802 for communicating with other network nodes, e.g.,other vehicles (e.g., the one or more other V-UEs 160), infrastructureaccess points (e.g., the one or more roadside access points 164), P-UEs(e.g., the one or more P-UEs 104), base stations (e.g., base stations102), etc., via at least one designated RAT (e.g., C-V2X or IEEE802.11p) over a medium of interest utilized by the unicast sidelinks162. The transceiver 804 may be variously configured for transmittingand encoding signals (e.g., messages, indications, information, and soon), and, conversely, for receiving and decoding signals (e.g.,messages, indications, information, pilots, and so on) in accordancewith the designated RAT. As used herein, a “transceiver” may include atransmitter circuit, a receiver circuit, or a combination thereof, butneed not provide both transmit and receive functionalities in alldesigns. For example, a low functionality receiver circuit may beemployed in some designs to reduce costs when providing fullcommunication is not necessary (e.g., a receiver chip or similarcircuitry simply providing low-level sniffing).

The UE 800 may also include a satellite positioning service (SPS)receiver 806. The SPS receiver 806 may be connected to the one or moreantennas 802 for receiving satellite signals. The SPS receiver 806 maycomprise any suitable hardware and/or software for receiving andprocessing SPS signals. The SPS receiver 806 requests information andoperations as appropriate from the other systems, and performs thecalculations necessary to determine the UE's 800 position usingmeasurements obtained by any suitable SPS algorithm.

One or more sensors 808 may be coupled to a processor 810 to provideinformation related to the state and/or environment of the UE 800, suchas speed, heading (e.g., compass heading), headlight status, gasmileage, etc. By way of example, the one or more sensors 808 may includea speedometer, a tachometer, an accelerometer (e.g., amicroelectromechanical systems (MEMS) device), a gyroscope, ageomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometricpressure altimeter), etc.

The processor 810 may include one or more microprocessors,microcontrollers, ASICs, and/or digital signal processors that provideprocessing functions, as well as other calculation and controlfunctionality. The processor 810 may include any form of logic suitablefor performing, or causing the components of the UE 800 to perform, atleast the techniques provided herein. In some aspects, the processor 810may include a modem processor to at least in part perform functions atthe PHY layer and MAC layer and an application processor configured atleast in part to perform functions at the application layer.

The processor 810 may also be coupled to a memory 814 for storing dataand software instructions for executing programmed functionality withinthe UE 800. The memory 814 may be on-board the processor 810 (e.g.,within the same integrated circuit (IC) package), and/or the memory 814may be external to the processor 810 and functionally coupled over adata bus.

The UE 800 may include a user interface 850 that provides any suitableinterface systems, such as a microphone/speaker 852, keypad 854, anddisplay 856 that allow user interaction with the UE 800. Themicrophone/speaker 852 provides for voice communication services withthe UE 800. The keypad 854 comprises any suitable buttons for user inputto the UE 800. The display 856 comprises any suitable display, such as,for example, a backlit liquid crystal display (LCD), and may furtherinclude a touch screen display for additional user input modes.

In an aspect, the UE 800 may include a geo-fence component 170functionally coupled to or integrated into the processor 810. Thegeo-fence component 170 may be a hardware, software, or firmwarecomponent that, when executed, causes the UE 800 to perform theoperations described herein. For example, the geo-fence component 170may be a software module stored in memory 814 and executable by theprocessor 810. As another example, the geo-fence component 170 may be ahardware circuit (e.g., an ASIC, a field programmable gate array (FPGA),etc.) within the UE 800. The functions of the of the geo-fence component170 will be discussed in greater detail below.

As discussed above, for example, a zone ID or an area ID may be encodedin the message to reduce overhead and allow a determination of arange/distance (e.g., based on zone IDs, layer IDs, etc.) between atransmitting UE and receiving UE that can be associated with a message.For example, the range information for the message may comprise acircular area centered on the location of the transmitting device, orother transmitter engaged in PC5 communication, and extending to aradius indicated to the receiving UEs. Also noted above, variousalternative zones may be defined, such as predefined zones includingnon-circular shapes, each having a corresponding zone ID or may follow acontour of a road, a driving direction, a shape of a geographic feature,etc. Also, as discussed, hierarchical zones may be organized indifferent layers, where each layer corresponds to zones of a differentsize (e.g., 50 m, 100 m, etc.) Accordingly, the transmitting device andreceiving device may identify the zone/area that is an intended range ofthe message based on a layer ID and/or a zone ID. In a specific example,a first UE may transmit a message with an intended range (e.g.,configured as a zone ID and/or range information) associated with themessage. A second UE may receive this message and use the zone ID and/orrange information to determine if the second UE is within a thresholdrange to act on the message. In the various aspects discussed herein,this determination can be performed at the PHY-MAC layer to reduce powerconsumption. If the receiving UE is within the threshold range, thesecond UE can enable application layer processing of the message. Forexample, zone ID/range information can be provided in sidelink controlinformation (SCI). Additionally, in some aspects, direction-basedcontrol (e.g., beamforming/beam steering can be used to improvesituational awareness and reduce RF congestion). It will be appreciatedthat if the first UE is moving, dynamic geo-fence boundaries can begenerated around the first UE based on the range information associatedwith the message (e.g., zone ID, etc.). Accordingly, in addition todetermining a zone/area/range for which the message is intended to bereliably received, discussed above, various aspects can determine toblock or permit application layer processing of the message based on arange threshold.

The various aspects disclosed include techniques for determiningproximity to a geo-fence and invoking action based on that proximity. Anexample action may be collision deterrence related actions. Otheractions may include, but are not limited to, visual, audible, haptic orother warnings or commands indicating motion state changes. As notedabove, existing wireless hazard alert systems require always-onbroadcast and application layer message processing, resulting inincreased power consumption and additional RF congestion. Variousaspects of the disclosure, create a “moving geo-fence” by exposing 5G NRPC5 PHY-MAC embedded controls to the application layer. Various aspectsof the disclosure also reduce device power consumption by repurposing 5GNR PC5 PHY-MAC control message mechanisms to enable or disableapplication layer message processing. For example, zone ID and/orrange-based control (e.g. sidelink control information (SCI) rangeand/or zone ID parameters). Additionally, direction-based control (e.g.beam steering to improve situational awareness and reduce RF congestion)may be provided. The reduced power consumption can be obtained forbattery-operated devices by disallowing upper layer processing andmessage transmission. High message reliability within the configuredthreshold range can be achieved through NR NACK-based reliability,discussed above. Additionally, dynamic geo-fence boundaries can begenerated around a PC5-device based on real-time proximity topedestrians, cyclists, animals, etc. Further, aspects of the presentdisclosure using PC5 provide greater range than otherinfrastructure-less vehicle communication, such as DSRC or IEEE 802.11p, which are also limited to broadcast operations.

According to various aspects disclosed herein, a proximity component candetermine inter-UE range using two control message parameters, zone IDand/or range information. According to various aspects, zone ID can bethe present UE location based on defined zones (as discussed herein) andrange can be defined either as a discrete number of zones or absolutedistance measurement. However, the various aspects disclosed herein arenot limited to these examples. These two control message parameters canalso be used at the PHY-MAC to control retransmission for highreliability. As noted above, the zone ID and range information can beused to determine the range between UEs at the PHY-MAC level. Thisallows for a virtual mobile geo-fence/dynamic geo-fence that moves withthe UE. In contrast, conventional architectures have range/positiondetermined at the application layer to provide a geo-fence which ispower intensive. In some UE configurations, a separate applicationprocessor may have to be activated to perform application layerprocessing, whereas the PHY-MAC layer operations may be performed at themodem level for even further power savings.

Conventionally, the PHY-MAC control message parameters are not visibleto the application layer. To provide for the various aspects of thedisclosure, additional functional modules are provided to enable ordisable application layer message processing based on the range andoptionally direction determination (based on zone ID and rangeinformation) embedded in D2D/C-V2X communications (e.g., 5G NR PC5communications), as discussed in the foregoing. As used herein, theterms D2D, C-V2X and/or PC5 information can include one or moreapplication layer messages, control messages and/or information relatedto inter-UE range determination (e.g., zone ID, range, etc.). Inaccordance with various aspects disclosed, the D2D, C-V2X and/or PC5information may be transmitted within a message container using theunicast sidelink mechanisms defined by the 3rd Generation PartnershipProject (3GPP). Other aspects may transmit the D2D, C-V2X and/or PC5information using other 3GPP cast types, such as broadcast or groupcast.Likewise, the term D2D, C-V2X and/or PC5 communication can include oneor more application layer messages, control messages/information relatedto inter-UE range determination (e.g., zone ID, range, etc.) transmittedover an air interface (e.g., PC5 interface). For convenience ofexplanation, the term PC5 communication will be used in the followingexample, but it will be appreciated that the various aspects disclosedcan be applied generally to D2D communications and devices.

In FIG. 9, a proximity component 900 is illustrated (which may besimilar to geo-fence component 170 in functionality). It will beappreciated that the various modules illustrated can communicate witheach other in a bidirectional fashion and may perform differentfunctions in a transmitting mode as opposed to a receiving mode. Forexample, in the application layer 910, an application layer basedspecification of a range threshold value (e.g., corresponding to thegeo-fence dimension in number of zones, absolute distance, etc.) can bedetermined in the range specification module 916. Optionally, anorientation (including two or more dimensions) can be provided to focusthe geo-fence to a specific vector/direction. The range threshold valuecan then be provided to the PHY-MAC layer 920. In a transmitting mode,the range threshold value can be provided to range module 922, which canthen use this information to be included in the PC5 communication toidentify the range (e.g., number of zones along with the devices currentzone ID) for which the message is intended to be received (e.g.,defining a geofence for the device). Optionally, the orientationinformation from range specification module 916 can be provided to thedirection module 926 which can then steer the RF signals of the PC5communication (including the range information) in a specific direction(e.g. toward a known road, etc.). In a receiving mode, optionally, an RXrange threshold value can be used in the threshold detection module 924to determine if the message received is within an RX threshold range,which may be different than a range that was received in a PC5communication. This receiver based range setting allows for analternative range control, separate from Tx based range control.Alternatively, the range threshold value may be determined at PHY-MAClayer 920 based on signal processing on the received communications(e.g., determined reliability threshold) and/or based on the rangeincluded in the PC5 communication from the transmitting device. In someaspects, the range in the PC5 communication defining a geographic area(e.g., zone ID and range) intended for the message, may be used todefine the range threshold value. However, in other aspects, the rangemay not be provided in the PC5 communications or the range may bereplaced by an RX range threshold value determined at the receiving UE.For example, a receiving UE may optionally define an RX range thresholdvalue to specify a minimum range of 2 adjacent zones. Accordingly, ifthe range received in the PC5 communication message is less than 2, theRX range threshold value could be used by the threshold detection module924 for determining whether the range threshold is met.

Regardless of where the range threshold value is specified (e.g.,determined from the received message, specified at application layer,determined at PHY-MAC layer, etc.), the threshold detection module 924can be configured to determine if an inter-UE range/range to thetransmitting UE is within a threshold range (e.g., violates thegeo-fence, proximity limit). For example, the range module 922 candetermine information such as zone ID of the transmitting UE and/orrange information (e.g., number of adjacent zones) from the received PC5communication (e.g., in SCI as discussed therein) from the transmittingUE. This information can be used by range module 922 to determine if thereceiving UE is within a threshold range. For example, being within thethreshold range may be determined from the range threshold value (e.g.,range received in the PC5 communication), the zone ID of thetransmitting UE and the zone ID of the receiving UE (e.g., the zone IDof the receiving UE is within 2 adjacent zones of the transmitting UE).Additionally, it will be appreciated that the threshold range value maybe determined so that proximity limit is violated if range determined isgreater than a threshold in some aspects. Accordingly, the thresholdrange may be violated in some configurations when inter-UE range is lessthan the threshold range value and in other configurations, thethreshold range may be violated when inter-UE range is greater than thethreshold range value.

In contrast to conventional systems that use GPS location at theapplication layer, it will be appreciated that in various aspectsdisclosed herein, the inter-UE range can be determined at the PHY-MAClayer 920. For example, if the threshold detection module 924 determinesbased on the geographic location (e.g. zone ID) of the receiving UE(containing threshold detection module 924) that the inter-UE range isgreater than range threshold value, subsequent application layermessages may not be passed to the application layer 910. Therefore, theapplication layer 910 modules would not be activated and power savingscan be achieved, as discussed herein. Blocking messages from theapplication layer 910, reduces UE power consumption by reducing both UEupper-layer processing (e.g., modules 912, 914, etc.) and reducingunnecessary message transmission (e.g., attempts to respond to message).If the inter-UE range is not greater than range threshold value (e.g.,within 2 adjacent zones), the application layer messages can be passedto the application layer 910. For example, the application layermessages can be passed to an application layer message processing module912 and based on the content of the application layer messages, in someaspects, the UE action module 914 can initiate specific actions based onthese messages. Application layer message elements can be provided tospecify UE action, if the receiving UE is determined to be within thethreshold range (e.g., within the geo-fence, proximity limit, number ofadjacent zones, and/or absolute distance from the transmitting UE). Forexample, when inter-UE range is not greater than the range thresholdvalue (e.g., the receiving UE is within a geo-fence for the transmittingUE) the receiving UE may perform one or more actions such as, initiate awarning (audio, haptic, and/or visual), initiate braking, steering,deceleration, and/or perform other actions to avoid collision. Examplesof the various messages discussed herein are provided in the followingparagraphs related to FIGS. 10 and 11.

As discussed above, the range threshold value may be derived from thePC5 communication received from the originating/transmitting UE based onthe zone ID of the originating UE and range information. For example,the originating UE may provide its zone ID and range information (e.g.,1 adjacent zone), to define a geographic area which a message in the PC5communication would be intended to be received and optionally actedupon. The receiving UE can then determine in range module 922 theoriginating UE zone ID and range information (e.g., 1 adjacent zone)from the PC5 communication. Threshold detection module 924 can use thegeographic area (e.g., originator zone ID and range information) todetermine if the current geographic location (e.g., zone ID of thereceiving UE) is less than or equal to the range threshold value (e.g.,1 adjacent zone). For example, if the receiving UE has the same zone IDor is located within 1 adjacent zone ID of the originating UE zone ID,then the receiving UE is within the range threshold and the applicationlayer processing would be enabled, as discussed above.

In an alternative example, as discussed above, an optional RX rangethreshold value may be established at the receiving UE (e.g., fromapplication layer 910). The originating UE may only provide a zone ID inthe PC5 communication (e.g., for some low power/limited devices) or therange provided may be overridden by the receiving UE based on its own RXrange threshold value. If the receiving UE determines the RX rangethreshold value is 1 adjacent zone, then the results would be the sameas the example with the range information (1 adjacent zone) provided inthe PC5 communication from the originating UE. Alternatively, ifreceiving UE determines the RX range threshold value is 2 adjacent zonesand is configured to override the range received in the PC5communication, then application layer messages provided in the PC5communication from the originating UE, would be processed at a greaterinter-UE range (e.g., up to 2 adjacent zones, instead of 1).

It will be appreciated that the determination of the inter-UE range, maytake any of the forms discussed herein and is not limited to thisspecific zone ID example. Further, it will be appreciated the zone IDand range information may represent any of a variety of configurations,as discussed herein. For example, the zone ID may be circular with agiven radius about the originating/transmitting UE location.Alternatively, the zone ID may be rectangular and, for example, 1adjacent zone may include 8 additional zones that are each adjacent toeach side and corners of the rectangular zone, defined by the zone ID ofthe originating UE. Alternatively, the range may be defined as anabsolute distance (e.g., 100 meters) from the geographic location of theoriginating/transmitting UE. Accordingly, it will be appreciated thatthe foregoing examples are provided merely for illustration and thespecific examples should not be construed to limit the various aspectsdisclosed herein.

In accordance with some additional aspects, instead of a one-dimensionalrange, the range information can be two or three dimensional asdetermined by direction module 926, which allows for beam steering tofocus the RF signals transmitted. The PHY-MAC layer 920 can optionallybe configured to enable beam steering using direction module 926 tosteer RF beam energy to the most situationally relevant location (e.g.,toward a known roadway, intersection, transmitting UE, away from anobstruction, etc.). Focusing the RF signals/energy in a specificdirection/vector can reduce unneeded RF congestion, RF noise and provideincreased situational awareness.

The foregoing has discussed the function of component 900 from primarilya receiving standpoint. As discussed above, various modules can be usedin transmitting operations. For example, a first UE be configured totransmit a message in a D2D communication (e.g., C-V2X, PC5, etc.). Themessage can include one or more data elements related to a geo-fence ofthe first UE. For example, the range specification module 916 canspecify a range to be associated with the message. The rangespecification module 916 can also optionally determine an orientation ofthe first UE relative to a potential receiving UE (e.g., toward aroadway, intersection, rail line, away from obstruction, etc.). Therange module 922 can identify the current geographic location of thefirst UE, which may be converted to a zone ID, and the range receivedfrom the range specification module 916 may be included with the zone IDto be transmitted (e.g., included in the SCI for a PC5 communication).The direction module 926 can optionally be used to steer RF signals(e.g., by beamforming and/or beam steering) to focus the energy of thetransmission in a direction of the potential receiving UE based on theorientation.

FIG. 10 illustrates data elements that may be used to augment existingapplication layer standard messages or be part of new application layermessages. Application layer messages may include those defined byindustry and government organizations, such as the Society of AutomotiveEngineers (SAE), the European Telecommunications StandardsInstitute—Intelligent Transportation Systems (ETSI-ITS), or others.Examples of existing application layer messages suitable forencapsulating application layer data elements (DEs) includes the SAEPersonal Safety Message (PSM), which is defined in the SAE specificationJ2735 “Dedicated Short Range Communications (DSRC) Message SetDictionary”. For example, new application data elements related toProximityAlertType, GeoFenceAlert and GeoFenceMotionInstruction may beincluded in the PSM according to various aspects disclosed herein. ThePSM is one example of an existing application layer message defined bythe SAE. Another example is a Basic Safety Message (BSM), however, it isnoted the data elements defined herein could be readily included inother existing SAE application layer messages as well. It will also beappreciated that the new application data elements could alternativelybe encapsulated in other messages for different standard groups (e.g.,IEEE, 3GPP, etc.). Accordingly, the various aspects disclosed herein arenot limited to the specific examples provided herein. According to someexample aspects, the ProximityAlertType data element includes variousentity types including pedestrian, cyclist, animal, vehicle and other.This data element can be used to alert a UE (e.g. vehicle, tag bearer,pedestrian, etc.) to the presence of an entity within a distancethreshold (e.g., vehicle alerted to tag bearer or tag bearer alerted tovehicle). The GeoFenceAlert data element includes various warning oraction types, such as an audible alert, haptic alert and other. Thisdata element can be used for a direct warning action. TheGeoFenceMotionInstruction data element can include an instruction toinitiate movement by a UE (e.g., vehicle, a tag bearer, etc.) in thedirection defined by an angle value (e.g., J2735 DE_Angle value). Itwill be appreciated that these messages, data elements and actions canaid in inter-UE range determination and detection of proximity to ageofence and/or can be used for various functions such as collisiondeterrence.

FIG. 11 illustrates new application layer messages according to aspectsof the disclosure. For example, a new message such as a proximity alertmessage and selected elements thereof may be provided, as illustrated.The new message can enable both request and response interaction betweenUEs (e.g., vehicle and device/tag bearer). The proximity alert messagemay have message parts including originator parameters and proximityalert components. The originator parameters content may includeidentity, statistic characteristics, dynamic characteristics, type:proximity alert request, and type: proximity alert response, forexample. The static characteristic identity may include a permanent UEidentifier, such as a license plate number, VIN number for a vehicle, anissued identifying number of alphanumeric code for a UE associated withan animal, an existing number or alphanumeric code for a UE associatedwith pedestrian, cyclist, scooter or other non-vehicle road user, or anumber or alphanumeric code assigned to the UE specifically forproximity-based geo-fence detection. Other static characteristics couldinclude vehicle type, vehicle size, color, or other descriptiveattributes. Static characteristics of cyclists, scooters, electric wheelbalance boards, mopeds or users or other non-vehicles could includewheel size, physical size, color, number of permitted riders, or otherstatic attributes. Dynamic characteristics could include attributesassociated with the current and permitted motion states of the UE ordevice containing the UE. Vehicle dynamic characteristics could includelocation, speed, linear acceleration, attitude, angular velocity, wherethese five attributes are measured along three orthogonal axes.Additional vehicle dynamic parameters could include turning radius,stopping distance. The proximity alert components may include dataelements including ProximityAlertType, GeoFenceAlert andGeoFenceMotionInstruction, according to various aspects disclosedherein. The ProximityAlertType data element includes various entitytypes including pedestrian, cyclist, animal and other. This data elementcan be used to alert a UE (e.g. vehicle, tag bearer) to the presence ofan entity within a range threshold (e.g., vehicle alerted to tag beareror tag bearer alerted to vehicle). The GeoFenceAlert data elementincludes various warning or action types, such as an audible alert,haptic alert and other. This data element can be used for a directwarning action. The GeoFenceMotionInstruction data element can includean instruction to initiate movement (e.g., by a tag bearer) in thedirection defined by an angle value (e.g., J2735 DE_Angle value). Itwill be appreciated that these messages, data elements and actions canaid in inter-UE range determination, detection of proximity to ageofence and/or can be used for various functions, such as, collisiondeterrence.

FIG. 12 illustrates an exemplary signal flow between a first UE (UE1)1230 (e.g., transmitting UE) and a second UE (UE2) 1220. It will beappreciated that the UE2 1220 and UE1 1230 may be a variety of devicesand the roles may change in various aspects. For example, in one aspectUE1 may be a vehicle and UE2 may be another device / tag bearer (e.g.,another vehicle, pedestrian, cyclist, animal, livestock, constructionequipment, farming equipment, etc.) according to various aspects of thedisclosure. It will be appreciated that UE2 1220 and UE1 1230 may besimilar to any of the UEs disclosed herein (e.g., UEs 104, 152, 160,182, 190 in FIG. 1, UEs 240 depicted in FIGS. 2A and 2B, any of UEs 310,350 in FIG. 3, etc.).

At 1202, D2D information (e.g., included in PC5 communication) istransmitted from UE2 1220 to UE1 1230. In some aspects, the PC5communication may be or include an existing application layer message,such as a PSM, including new data elements (see, e.g., data elements inFIG. 10) Alternatively, the PC5 communication may consist of newapplication layer messages including the new data elements (see, e.g.,data elements in FIG. 10). Upon receipt of the PC5 communication, adetermination is made if the UE2 1220 (transmitting UE) is within thethreshold range, at 1204. As discussed above, this determination can beperformed at the PHY-MAC, and in some aspects may be performed withoutGPS assistance. If the UE2 1220 is determined not to be within thethreshold range, the PC5 communication (e.g., application layer message,data elements, etc.) is not provided to the application layer, at 1205.If the UE2 1220 is determined to be within the threshold range, the PC5communication is provided to the application layer and/or theapplication layer processing is enable for the received PC5communication, at 1206. At 1208, optionally, a high reliabilitytransmission is enabled by the UE1 1230 for communication with the UE21220. In some aspects, a high reliability transmission may include thatwhen the transmitter and receiver are close enough, the receiver (e.g.,UE1 1230) may affirmatively NACK a known transmission that was notreceived correctly or may be configured to affirmatively ACK receivedtransmissions (as discussed in the foregoing). At 1210, optionally, thenew data elements in the received D2D information (e.g., applicationlayer message) are acted upon by the UE1 1230. For example, analarm/alert could be activated, a movement initiated, etc. However, itwill be appreciated that in some aspects, the message may not be actedupon directly.

It will be appreciated that in other aspects the message receiving UE,UE1 1230 may be the vehicle and the transmitting UE2 1220 may be adevice/tag bearer (e.g., another vehicle, pedestrian, cyclist, animal,livestock, construction equipment, farming equipment, etc.) according tovarious aspects of the disclosure. Additionally, the D2D information isnot limited to the PC5 communication and/or the application layermessage examples used in the foregoing. Accordingly, it will beappreciated that the foregoing examples are provided merely forillustration and the specific examples should not be construed to limitof the various aspects disclosed herein.

FIG. 13 illustrates an exemplary signal flow between atransmitting/originating UE2 1320 (e.g., a device/tag bearer) and amessage receiving UE1 1330 (e.g., vehicle), according to aspects of thedisclosure. It will be appreciated that the UE1 1330 and UE2 1320 may bea variety of devices and the roles may change in various aspects. Forexample, in one aspect UE2 1320 may be a vehicle and UE1 1330 may beanother device/tag bearer (e.g., another vehicle, pedestrian, cyclist,animal, livestock, construction equipment, farming equipment, etc.)according to various aspects of the disclosure. It will be appreciatedthat UE2 1320 and UE1 1330 may be similar to any of the UEs disclosedherein (e.g., UEs 104, 152, 160, 182, 190 in FIG. 1, UEs 240 depicted inFIGS. 2A and 2B, any of UEs 310, 350 in FIG. 3, etc.).

At 1302, D2D information (e.g., a PC5 communication) is transmitted fromUE2 1320 to a message receiving UE, UE1 1330. In some aspects, incontrast to the previous example using an existing message, the PC5communication may be or include a new message, such as aProximityAlertRequest (see, e.g., FIG. 11). Upon receipt of the PC5communication, a determinations is made if the UE2 1320 (transmittingUE/transmitter) is within the threshold range, at 1304. As discussedabove, this determination is performed at the PHY-MAC, and in someaspects may be performed without GPS assistance. If the UE2 1320 isdetermined not to be within the threshold range, the PC5 communication(e.g., new message, data elements, etc.) is not provided to theapplication layer, at 1305. If the UE2 1320 is determined to be withinthe threshold range, the PC5 communication is provided to theapplication layer and/or the application layer is enabled for processingthe received PC5 communication, at 1306. At 1308, optionally, a highreliability transmission is enabled by UE1 1330 for communication withUE2 1320. As discussed above, in some aspects, a high reliabilitytransmission may include that when the transmitter and receiver areclose enough, the receiver (e.g., UE1 1330) may affirmatively NACK aknown transmission that was not received or may be configured toaffirmatively ACK received transmissions. At 1310, optionally, theactions specified in in the PC5 communication (e.g.,ProximityAlertRequest) are acted upon by the UE1 1330. At 1312, the PC5communication (e.g., ProximityAlertRequest) from UE2 1320 is respondedto (e.g., ProximityAlertResponse) in a transmission from the UE1 1330back to UE2 1320. In some aspects, the ProximityAlertResponse maycontain similar elements such as alert type, geofence alert action,receivers location (optionally), an entity identifier (i.e. a vehicle IDnumber, VIN, etc.), geofence motion instructions accepted or to beinitiated.

It will be appreciated that the D2D information is not limited to thePC5 communication, ProximityAlertRequest and/or ProximityAlertResponseexamples used in the foregoing. Accordingly, it will be appreciated thatthe foregoing examples are provided merely for illustration and thespecific examples should not be construed to limit of the variousaspects disclosed herein.

FIG. 14 illustrates an exemplary signal flow between a first UE, UE11420, (e.g., message receiving UE) and a second UE, UE2 1430, (e.g.,transmitting UE), according to some aspects of the disclosure. Forexample, in one aspect UE1 1420 may be a vehicle and UE2 1430 may beanother device/tag bearer (e.g., another vehicle, pedestrian, cyclist,animal, livestock, construction equipment, farming equipment, etc.)according to various aspects of the disclosure. It will be appreciatedthat UE1 1420 and UE2 1430 may be similar to any of the UEs disclosedherein (e.g., UEs 104, 152, 160, 182, 190 in FIG. 1, UEs 240 depicted inFIGS. 2A and 2B, any of UEs 310, 350 in FIG. 3, etc.).

At 1401, the transmitting UE2 1430 can optionally, steer RF signalstransmitted toward UE 1420 as part of a D2D message/information (e.g.,PC5 communications such as discussed above) being transmitted from UE21430 to UE1 1420, at 1302. It will be appreciated that beamformingand/or beam steering may be used to direct the RF signals transmitted/RFtransmission power toward a general location/direction of UE1 1420. Forexample, even if UE2 1430 does not know the specific location of UE11420 (or even if there is a UE1 1420) it may be able to direct the RFsignals transmitted toward a location or direction where a UE is likelyto be (e.g., road, intersection, bicycle path, hiking path, railway,etc.). It will be appreciated that the optional RF steering aspect mayreduce RF/channel congestion, improve transmission reliability, andreduce power consumption among other benefits. For example, if UE2 1430is a pedestrian in an urban environment, the initial beam steering couldbe based on the pedestrian's orientation and/or direction of motion andany roads or intersections in the orientation and/or direction of motionof the pedestrian. The RF signals transmitted/RF transmission powerwould not be directed towards adjacent buildings, behind the pedestrian,etc. to reduce power consumed by the device and improve reliabletransmission by reducing RF noise floor, which improve the performanceof the transmitting device and other devices in the wirelesscommunications network. Likewise, if UE2 1430 was a tagged animal in arural environment, the initial beam steering could be directed towards aknown road, intersection, hiking path, etc. based on an orientationand/or direction of motion of the tagged animal. The RF signalstransmitted/RF transmission power would not be directed towards off-roadareas which could reduce power consumed by the device.

Regardless of the transmission technique, upon receipt of the PC5communication, a determination is made if the UE1 1420 is within thethreshold range, at 1404. As discussed above, this determination can beperformed at the PHY-MAC, and in some aspects may be performed withoutGPS assistance. Additionally, in some aspects, it may be determined thatUE2 is within the threshold range, as the determination is based on theinter-UE range/distance between UE1 and UE2, as discussed in theforegoing. If the UE1 1420 is determined not to be within the thresholdrange, the PC5 communication (e.g., application layer message) is notprovided to the application layer, at 1405. If the UE1 1420 isdetermined to be within the threshold range, the PC5 communication isprovided to the application layer and in some aspects the applicationlayer processing is enabled to process the received PC5 communication,at 1406. Optionally, at 1408, high reliability transmission is enabledat the UE1 1420 for communication with the UE2 1430, as discussed in theforegoing disclosure. At 1410, optionally, the actions specified in inthe PC5 communication (e.g., application layer message,ProximityAlertRequest, etc.) are acted upon by the UE1 1420. At 1411,optionally, UE1 1430 can steer the RF signals toward UE2 1430 whenresponding to the D2D message/information (e.g., PC5 communications suchas discussed above) being received from UE2 1430. For example, theD2D/PC5 communication from UE2 1430 (e.g., application layer message,ProximityAlertRequest, etc.) may include a request a response, which canbe responded to (e.g., ProximityAlertResponse) in a transmission fromthe UE1 1420 back to UE2 1430, at 1412.

It will be appreciated that in other aspects the message receiving UE,UE1 1420 may be another device/tag bearer (e.g., another vehicle,pedestrian, cyclist, animal, livestock, construction equipment, farmingequipment, etc.) according to various aspects of the disclosure.Additionally, the beamforming/beam steering aspects discussed above maybe used in some configurations but not in others. For example, the RFsignal/beam steering of 1401 of the D2D information transmission 1402may be used regardless of whether there will be a response to D2Dinformation and/or RF signal/beam steering (e.g., 1411) used in theresponse. Likewise, in some aspects, the RF signal/beam steering 1411 ofthe response to the D2D information may be used regardless of whether RFsignal/beam steering was used in the transmission of the D2Dinformation. Accordingly, it will be appreciated that the foregoingexamples are provided merely for illustration and the specific examplesshould not be construed to limit of the various aspects disclosedherein.

It will be appreciated from the foregoing that the various aspectsdiscussed and disclosed herein include methods for determining aproximity to a geo-fence and optionally invoking actions based on theproximity for various applications, such as collision deterrence. FIG.15 illustrates a flowchart of method 1500 according to at least oneaspect of the disclosure. The method 1500 may be performed by a first UE(e.g., similar to any of the UEs disclosed herein (e.g., UEs 104, 152,160, 182, 190 in FIG. 1, UEs 240 depicted in FIGS. 2A and 2B, any of UEs310, 350 in FIG. 3, etc.). At block 1502, the first UE (e.g., vehicle,tag bearer, pedestrian, etc.) receives device to device (D2D)information from a second UE (e.g., vehicle, tag bearer, pedestrian,etc.). At block 1504, the first UE can determine whether the first UE iswithin a threshold range from the second UE based on the D2D information(e.g., as noted above this can be performed at the PHY-MAC layer). Atblock 1506, the first UE can enable application layer processing of amessage in the D2D information (e.g., this can include new data elementscontained in existing application layer messages (e.g., SAE PSM) or newmessages, as discussed above), if the first UE is within the thresholdrange (i.e., “Yes” in the flowchart). At block 1516, the first UE canblock the message from the application layer (e.g., at the PHY-MAC asdiscussed above), if the first UE is not within the threshold range(i.e., “No” path in the flowchart). As discussed in the foregoing, thiscan allow for significant power savings, since the application layerprocessor and/or processing functions would not be initialized. At block1508, the first UE can optionally enable high reliability transmission,if the first UE is within the threshold range. For example, as discussedabove, to improve reliability, feedback may be sent back from thereceiving UE (first UE). For example, if the first UE does not correctlyreceive the D2D information (e.g., PC5 communication), the first UE maytransmit a NACK, (e.g., via PC5 communications) indicating to the secondUE that there was an error in receiving the message. In response to theNACK, the second UE may retransmit the message. Additionally,beamforming and/or beam steering may also be used to steer the RFsignals/beams toward the second UE, as discussed above. At block 1510,the first UE can optionally, perform one or more actions at the first UEbased on one or more data elements of the message (e.g., alerts, motion,etc. as discussed in the foregoing). It will be appreciated from thedisclosure herein that other methods and variations of methods can berecognized and detailed flowcharts and/or discussion of each will not beprovided. For example, in various aspects, a response to the receivedD2D information may be transmitted from the first UE to the second UE.The transmitted response may optionally use beamforming/beam steering tomore precisely direct the RF transmission to the second UE, as discussedherein. Accordingly, the various aspects of the disclosure should not beconstrued to be limited to the illustrative examples provided.

It will be appreciated from the foregoing that the various aspectsdiscussed and disclosed herein include methods for transmitting anapplication layer message (e.g., personal safety message), which mayinclude new data elements discussed herein (e.g., see FIG. 10) and/ornew messages (e.g., see FIG. 11) related to a geo-fence of atransmitting UE. FIG. 16A illustrates a flowchart of method 1610. Themethod 1610 for wireless communication is performed at a first userequipment (UE) 1601. In block 1602, the first UE receives adevice-to-device (D2D) communication from a second user equipment (UE)including an application layer message (either an existing message, suchas the PSM or a new message) that includes one or more data elementsrelated to a geo-fence for the second UE. In various other aspects theapplication layer message (either an existing message, such as the PSMor a new message) can be included as the message included in the D2Dinformation including the range information to allow for thedetermination of the geo-fence and geo-fence violations, as detailed inthe foregoing. Likewise, the first UE and second UE may be any of thevarious UEs disclosed herein. Accordingly, it will be appreciated fromthe disclosure herein that other methods and variations of methods canbe recognized and detailed flowcharts and/or discussion of each will notbe provided. Accordingly, the various aspects of the disclosure shouldnot be construed to be limited to the illustrative examples provided.

FIG. 16B illustrates a flowchart of method 1620. The method 1620 forwireless communication is performed at a user equipment (UE) 1621. At1622 the UE transmits a device-to-device (D2D) communication, whereinthe D2D communication includes an application layer message (e.g.,either an existing message, such as the PSM with new data elements or anew message) and the application layer message includes one or more dataelements related to a geo-fence for the UE. The method can optionallyinclude at 1624 determining an orientation of the UE relative to apotential receiving UE. It will be appreciated an orientation/directiontowards one or more potential receiving UEs (e.g., toward a road, awayfrom an obstruction, etc., as discussed in the foregoing). The termpotential receiving UEs is used as the transmitting UE may not know ifthere are any UEs within a transmission range that can receive thetransmission. The method can also optionally include at 1626 steering RFsignals of the transmission in a direction of the potential receiving UEbased on the orientation. As discussed above, steering the RF signalscan be performed by beamforming and/or beam steering to focus the RFsignals/transmission power, which can reduce energy consumption, improvesituational awareness and reduce RF congestion among other benefits, asdiscussed herein.

In various other aspects the UE can determine a geographic location(e.g., zone ID, area ID, etc.) of the UE and a range for the geo-fence,which can be used for the D2D information the determination of thegeo-fence and geo-fence violations, as detailed in the foregoing.Likewise, the UE and potential receiving UE may be any of the variousUEs disclosed herein. Accordingly, it will be appreciated from thedisclosure herein that other methods and variations of methods can berecognized and detailed flowcharts and/or discussion of each will not beprovided. Accordingly, the various aspects of the disclosure should notbe construed to be limited to the illustrative examples provided.

The functionality of the various devices, components, methods, etc.disclosed herein may be implemented in various ways consistent with theteachings herein. In some designs, the functionality of these modulesmay be implemented as one or more electrical components. In somedesigns, the functionality of these blocks may be implemented as aprocessing system including one or more processor components. In somedesigns, the functionality of these modules may be implemented using,for example, at least a portion of one or more integrated circuits(e.g., an ASIC). As discussed herein, an integrated circuit may includea processor, software, other related components, or some combinationthereof. Thus, the functionality of different modules may beimplemented, for example, as different subsets of an integrated circuit,as different subsets of a set of software modules, or a combinationthereof. Also, it will be appreciated that a given subset (e.g., of anintegrated circuit and/or of a set of software modules) may provide atleast a portion of the functionality for more than one module.

FIG. 17 illustrates an example proximity-based geo-fence device 1700(which may be similar to geo-fence component 170 and/or component 900)for implementing various aspects of the disclosure, which arerepresented as a series of interrelated functional modules. The device1700 may correspond to any of the UEs disclosed herein (e.g., UEs 104,152, 160, 182, 190 in FIG. 1, UEs 240 depicted in FIGS. 2A and 2B, anyof UEs 310, 350 in FIG. 3, etc.). In the illustrated example, a module1702 for receiving D2D information (e.g., a PC5 communication) from asecond user equipment (UE); may correspond at least in some aspects to,for example, a communication device (e.g., transceiver 804 and/or aprocessing system (e.g., processors 810), etc.) as discussed herein. Amodule 1704 for determining whether the first UE is within a thresholdrange (inter-UE range between first UE and second UE, as discussedabove) based on the D2D information, may correspond at least in someaspects to, for example, a communication device (e.g., transceiver 804,and/or a processing system, e.g., processor 810) and in some aspects maybe functions of the PHY-MAC layers (e.g., including functionality suchas range module 922 and/or threshold detection module 924) of a modemprocessor, as discussed herein. A module 1706 for enabling applicationlayer processing of one or more data elements of the D2D informationreceived, if the first UE is within the threshold range, and maycorrespond at least in some aspects to, for example, a processing device(e.g., processor 810, etc.) as discussed herein and in some aspects toan application layer processor that performs processing at anapplication layer (e.g., 910). A module 1707 for blocking the messagefrom the application layer, if the first UE is not within the thresholdrange, may correspond at least in some aspects to, for example, acommunication device (e.g., transceiver 804 and/or a processing systeme.g., processor 810) and in some aspects may be functions of the PHY-MAClayers (e.g., threshold detection module 924) of a modem processor, asdiscussed herein. An optional module 1708, for enabling high reliabilitytransmission, if the first UE is within a threshold range from thesecond UE, may correspond at least in some aspects to a communicationdevice (e.g., transceiver 804 and/or a processing system, e.g.,processor 810). Another optional module 1710 for performing one or moreactions at the first UE based on the one or more data elements in themessage, may be for example, a processing system (e.g., processor 810)or may be an application processor configured to perform functions atthe application layer (e.g., 910, 914), as discussed herein. Anotheroptional module 1711, for steering RF signals of the transmission, maycorrespond at least in some aspects to a communication device (e.g.,transceiver 804 and/or a processing system, e.g., processor 810) and insome aspects may be functions of the PHY-MAC layers (e.g., directionmodule 926) and/or beam forming functions of a modem processor, asdiscussed herein. It will be appreciated that depending on theconfiguration, module 1711 may be used for steering RF signals in aninitial (originating) transmission toward an intended direction and/orfor steering RF signals toward an originating UE, when responding to thetransmissions from the originating UE, as discussed herein.

In addition, the modules, components and/or functions represented byFIGS. 9 and 17, as well as other modules, components and/or functionsdescribed herein, may be implemented using any suitable means. Suchmeans also may be implemented, at least in part, using correspondingstructure as taught herein. For example, the components described abovein conjunction with the “module for” also may correspond to similarlydesignated “means for” functionality. Thus, in some aspects one or moreof such means may be implemented using one or more processors, memory,integrated circuits, or other suitable structure as taught herein,including as an algorithm. One skilled in the art will recognize in thisdisclosure an algorithm may be represented in the functions, actions,etc. described above, as well as in sequences of actions that may berepresented by pseudocode. For example, the components, modules and/orfunctions represented by FIGS. 9 and 17 may include code for performingthe functions, aspects and actions disclosed herein. .

Those of skill in the art will appreciate that information and signalsmay be represented using any of a variety of different technologies andtechniques. For example, data, instructions, commands, information,signals, bits, symbols, and chips that may be referenced throughout theabove description may be represented by voltages, currents,electromagnetic waves, magnetic fields or particles, optical fields orparticles, or any combination thereof.

Further, those of skill in the art will appreciate that the variousillustrative logical blocks, modules, circuits, and algorithm stepsdescribed in connection with the aspects disclosed herein may beimplemented as electronic hardware, computer software, or combinationsof both. To clearly illustrate this interchangeability of hardware andsoftware, various illustrative components, blocks, modules, circuits,and steps have been described above generally in terms of theirfunctionality. Whether such functionality is implemented as hardware orsoftware depends upon the particular application and design constraintsimposed on the overall system. Skilled artisans may implement thedescribed functionality in varying ways for each particular application,but such implementation decisions should not be interpreted as causing adeparture from the scope of the present disclosure.

The various illustrative logical blocks, modules, and circuits describedin connection with the aspects disclosed herein may be implemented orperformed with a general purpose processor, a DSP, an ASIC, an FPGA, orother programmable logic device, discrete gate or transistor logic,discrete hardware components, or any combination thereof designed toperform the functions described herein. A general purpose processor maybe a microprocessor, but in the alternative, the processor may be anyconventional processor, controller, microcontroller, or state machine. Aprocessor may also be implemented as a combination of computing devices,e.g., a combination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration.

The methods, sequences and/or algorithms described in connection withthe aspects disclosed herein may be embodied directly in hardware, in asoftware module executed by a processor, or in a combination of the two.A software module may reside in random access memory (RAM), flashmemory, read-only memory (ROM), erasable programmable ROM (EPROM),electrically erasable programmable ROM (EEPROM), registers, hard disk, aremovable disk, a CD-ROM, or any other form of storage medium known inthe art. An exemplary storage medium is coupled to the processor suchthat the processor can read information from, and write information to,the storage medium. In the alternative, the storage medium may beintegral to the processor. The processor and the storage medium mayreside in an ASIC. The ASIC may reside in a UE. In the alternative, theprocessor and the storage medium may reside as discrete components in aUE.

In one or more exemplary aspects, the functions described may beimplemented in hardware, software, firmware, or any combination thereof.If implemented in software, the functions may be stored on ortransmitted over as one or more instructions or code on acomputer-readable medium. Computer-readable media includes both computerstorage media and communication media including any medium thatfacilitates transfer of a computer program from one place to another. Astorage media may be any available media that can be accessed by acomputer. By way of example, and not limitation, such computer-readablemedia can comprise RAM, ROM, EEPROM, CD-ROM or other optical diskstorage, magnetic disk storage or other magnetic storage devices, or anyother medium that can be used to carry or store desired program code inthe form of instructions or data structures and that can be accessed bya computer. Disk and disc, as used herein, includes compact disc (CD),laser disc, optical disc, digital versatile disc (DVD), floppy disk andBlu-ray disc where disks usually reproduce data magnetically, whilediscs reproduce data optically with lasers. Combinations of the aboveshould also be included within the scope of computer-readable media.

While the foregoing disclosure shows illustrative aspects of thedisclosure, it should be noted that various changes and modificationscould be made herein without departing from the scope of the disclosureas defined by the appended claims. The functions, steps and/or actionsof the method claims in accordance with the aspects of the disclosuredescribed herein need not be performed in any particular order.Furthermore, although elements of the disclosure may be described orclaimed in the singular, the plural is contemplated unless limitation tothe singular is explicitly stated.

1. A method for wireless communication at a first user equipment (UE),comprising: receiving a device-to-device (D2D) communication from asecond user equipment (UE) including an application layer message,wherein the application layer message includes one or more data elementsrelated to a geo-fence for the second UE; determining whether the firstUE is within the geo-fence of the second UE based on the D2Dcommunication; and enabling application layer processing of theapplication layer message, if the first UE is within the geo-fence ofthe second UE.
 2. (canceled)
 3. The method of claim 1, furthercomprising: enabling high reliability transmission at the first UE, ifthe first UE is within the geo-fence of the second UE.
 4. The method ofclaim 1, further comprising: performing one or more actions at the firstUE based on the one or more data elements of the application layermessage.
 5. A method for wireless communication at a first userequipment (UE), comprising: receiving a device-to-device (D2D)communication from a second user equipment (UE) including an applicationlayer message, wherein the application layer message includes one ormore data elements related to a geo-fence for the second UE; wherein theone or more data elements are encapsulated in the application layermessage; and wherein the one or more data elements encapsulated includeat least one of a ProximityAlertType data element, a GeoFenceAlert dataelement or a GeoFenceMotionInstruction data element.
 6. The method ofclaim 5, wherein the application layer message is a Society ofAutomotive Engineers (SAE) application layer message including at leastone of a Basic Safety Message (BSM) or a Personal Safety Message (PSM).7. (canceled)
 8. The method of claim 5, wherein the ProximityAlertTypedata element includes entity types including pedestrian, cyclist,animal, vehicle or other.
 9. The method of claim 5, wherein theGeoFenceAlert data element includes a warning or an action, including anaudible alert, haptic alert or other alert.
 10. The method of claim 5,wherein the GeoFenceMotionInstruction data element includes aninstruction to initiate movement.
 11. The method of claim 1, wherein theapplication layer message is a proximity alert message.
 12. The methodof claim 11, wherein the proximity alert message enables both requestand response interaction between the first UE and the second UE.
 13. Themethod of claim 11, wherein the proximity alert message includesoriginator parameters and proximity alert components.
 14. The method ofclaim 13, wherein the originator parameters includes at least one ofidentity, statistic characteristics, dynamic characteristics, type:proximity alert request, or type: proximity alert response.
 15. Themethod of claim 13, wherein the proximity alert components include dataelements including includes at least one of a ProximityAlertType dataelement, a GeoFenceAlert data element and a GeoFenceMotionInstructiondata element.
 16. The method of claim 15, wherein the ProximityAlertTypedata element includes an entity types including pedestrian, cyclist,animal, vehicle or other.
 17. The method of claim 15, wherein theGeoFenceAlert data element includes a warning or an action, including anaudible alert, haptic alert or other alert.
 18. The method of claim 15,wherein the GeoFenceMotionInstruction data element includes aninstruction to initiate movement.
 19. The method of claim 1, wherein theapplication layer message includes a response request.
 20. The method ofclaim 19, further comprising: transmitting a response to the second UEbased, if the second UE is within the geo-fence.
 21. A method forwireless communication at a user equipment (UE), comprising:transmitting a device-to-device (D2D) communication, wherein the D2Dcommunication includes an application layer message, and wherein theapplication layer message includes one or more data elements related toa geo-fence for the UE; wherein the one or more data elements areencapsulated in the application layer message; and wherein the one ormore data elements encapsulated include at least one of aProximityAlertType data element, a GeoFenceAlert data element or aGeoFenceMotionInstruction data element.
 22. (canceled)
 23. The method ofclaim 21, wherein the application layer message is a Society ofAutomotive Engineers (SAE) application layer message including at leastone of a Basic Safety Message (BSM) or a Personal Safety Message (PSM).24. (canceled)
 25. The method of claim 21, wherein theProximityAlertType data element includes entity types includingpedestrian, cyclist, animal, vehicle or other.
 26. The method of claim21, wherein the GeoFenceAlert data element includes a warning or anaction, including an audible alert, haptic alert or other alert.
 27. Themethod of claim 21, wherein the GeoFenceMotionInstruction data elementincludes an instruction to initiate movement.
 28. The method of claim21, wherein the application layer message is a proximity alert message.29. The method of claim 28, wherein the proximity alert message enablesboth request and response interaction between the UE and a potentialreceiving UE.
 30. The method of claim 28, wherein the proximity alertmessage includes originator parameters and proximity alert components.31. The method of claim 30, wherein the originator parameters includesat least one of identity, statistic characteristics, dynamiccharacteristics, type: proximity alert request, or type: proximity alertresponse.
 32. The method of claim 30, wherein the proximity alertcomponents include data elements including includes at least one of aProximityAlertType data element, a GeoFenceAlert data element and aGeoFenceMotionInstruction data element.
 33. The method of claim 32,wherein the ProximityAlertType data element includes an entity typesincluding pedestrian, cyclist, animal, vehicle or other.
 34. The methodof claim 32, wherein the GeoFenceAlert data element includes a warningor an action, including an audible alert, haptic alert or other alert.35. The method of claim 32, wherein the GeoFenceMotionInstruction dataelement includes an instruction to initiate movement.
 36. The method ofclaim 21, further comprising: determining an orientation of the UErelative to a potential receiving UE.
 37. The method of claim 36,further comprising: steering radio frequency (RF) signals of thetransmission of the D2D communication in a direction of the potentialreceiving UE based on the orientation.
 38. The method of claim 37,wherein steering the RF signals is performed by beamforming and/or beamsteering.
 39. The method of claim 37, wherein steering the RF signalsfurther comprises at least one of: directing the RF signals in adirection of a known roadway, or directing the RF signals in a directionof away from an obstruction.
 40. The method of claim 21, furthercomprising: determining a geographic location of the UE; and determininga range for the geo-fence of the UE.
 41. A first user equipment (UE)comprising: a transceiver; and at least one processor coupled to amemory and to the transceiver, the at least one processor in cooperationwith the transceiver being configured to: receive a device-to-device(D2D) communication from a second user equipment (UE) including anapplication layer message, wherein the application layer messageincludes one or more data elements related to a geo-fence for the secondUE; determine whether the first UE is within the geo-fence of the secondUE based on the D2D communication; and enable application layerprocessing of the application layer message, if the first UE is withinthe geo-fence of the second UE.
 42. (canceled)
 43. The first UE of claim41, wherein the at least one processor configured to: perform one ormore actions at the first UE based on the one or more data elements ofthe application layer message.
 44. A first user equipment (UE)comprising: a transceiver; and at least one processor coupled to amemory and to the transceiver, the at least one processor in cooperationwith the transceiver being configured to: receive a device-to-device(D2D) communication from a second user equipment (UE) including anapplication layer message, wherein the application layer messageincludes one or more data elements related to a geo-fence for the secondUE; wherein the one or more data elements are encapsulated in theapplication layer message; and wherein the one or more data elementsencapsulated include at least one of a ProximityAlertType data element,a GeoFenceAlert data element or a GeoFenceMotionInstruction dataelement.
 45. The first UE of claim 44, wherein the application layermessage is a Society of Automotive Engineers (SAE) application layermessage.
 46. (canceled)
 47. The first UE of claim 41, wherein theapplication layer message is a proximity alert message.
 48. The first UEof claim 47, wherein the proximity alert message includes originatorparameters and proximity alert components.
 49. The first UE of claim 48,wherein the proximity alert components include data elements includingincludes at least one of a ProximityAlertType data element, aGeoFenceAlert data element and a GeoFenceMotionInstruction data element.50. The first UE of claim 49, wherein the proximity alert componentsinclude data elements including includes at least one of aProximityAlertType data element, a GeoFenceAlert data element and aGeoFenceMotionInstruction data element, wherein the ProximityAlertTypedata element includes an entity types including pedestrian, cyclist,animal, vehicle or other, wherein the GeoFenceAlert data elementincludes a warning or an action, including an audible alert, hapticalert or other alert and wherein the GeoFenceMotionInstruction dataelement includes an instruction to initiate movement.
 51. A userequipment (UE) comprising: a transceiver; and at least one processorcoupled to a memory and to the transceiver, the at least one processorin cooperation with the transceiver being configured to: transmit adevice-to-device (D2D) communication, wherein the D2D communicationincludes an application layer message, and wherein the application layermessage includes one or more data elements related to a geo-fence forthe UE; wherein the one or more data elements are encapsulated in theapplication layer message; and wherein the one or more data elementsencapsulated include at least one of a ProximityAlertType data element,a GeoFenceAlert data element or a GeoFenceMotionInstruction dataelement.
 52. (canceled)
 53. The UE of claim 51, wherein the applicationlayer message is a Society of Automotive Engineers (SAE) applicationlayer message.
 54. (canceled)
 55. The UE of claim 51, wherein theapplication layer message is a proximity alert message.
 56. The UE ofclaim 55, wherein the proximity alert message includes originatorparameters and proximity alert components, wherein the proximity alertcomponents include data elements including includes at least one of aProximityAlertType data element, a GeoFenceAlert data element and aGeoFenceMotionInstruction data element.
 57. The UE of claim 56, whereinthe ProximityAlertType data element includes an entity types includingpedestrian, cyclist, animal, vehicle or other, wherein the GeoFenceAlertdata element includes a warning or an action, including an audiblealert, haptic alert or other alert and wherein theGeoFenceMotionInstruction data element includes an instruction toinitiate movement.
 58. The UE of claim 51, wherein the at least oneprocessor is further configured to: determine an orientation of the UErelative to a potential receiving UE.
 59. The UE of claim 58, whereinthe transceiver is configured to steer RF signals of the transmission ina direction of the potential receiving UE based on the orientation. 60.The UE of claim 51, wherein the at least one processor is furtherconfigured to: determine a geographic location of the UE; and determinea range for the geo-fence of the UE.